chore(deps): update ghcr.io/datasharingframework/bpe docker tag to v2 #414
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅
|
| Descriptor | Linter | Files | Fixed | Errors | Warnings | Elapsed time |
|---|---|---|---|---|---|---|
| ✅ ACTION | actionlint | 6 | 0 | 0 | 0.04s | |
| ✅ DOCKERFILE | hadolint | 8 | 0 | 0 | 0.47s | |
| ✅ EDITORCONFIG | editorconfig-checker | 51 | 0 | 0 | 0.03s | |
| ✅ JSON | jsonlint | 6 | 0 | 0 | 0.15s | |
| ✅ JSON | prettier | 6 | 0 | 0 | 0.58s | |
| ✅ JSON | v8r | 6 | 0 | 0 | 7.54s | |
| markdownlint | 9 | 6 | 0 | 1.02s | ||
| ✅ REPOSITORY | checkov | yes | no | no | 23.97s | |
| ✅ REPOSITORY | gitleaks | yes | no | no | 0.44s | |
| ✅ REPOSITORY | git_diff | yes | no | no | 0.03s | |
| kics | yes | no | 2 | 3.92s | ||
| ✅ REPOSITORY | secretlint | yes | no | no | 1.73s | |
| ✅ REPOSITORY | syft | yes | no | no | 9.21s | |
| trivy | yes | 8 | 2 | 12.73s | ||
| ✅ REPOSITORY | trivy-sbom | yes | no | no | 1.62s | |
| ✅ REPOSITORY | trufflehog | yes | no | no | 13.96s | |
| ✅ YAML | prettier | 9 | 0 | 0 | 0.51s | |
| ✅ YAML | v8r | 9 | 0 | 0 | 7.89s | |
| ✅ YAML | yamllint | 9 | 0 | 0 | 0.51s |
Detailed Issues
⚠️ REPOSITORY / kics - 2 warnings
warning: The 'Dockerfile' contains the 'chown' flag
┌─ images/ml-on-fhir/Dockerfile:43:1
│
43 │ COPY --chown=${NB_UID}:${NB_GID} requirements.txt /tmp/
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
│
= Chown Flag Exists
= It is considered a best practice for every executable in a container to be owned by the root user even if it is executed by a non-root user, only execution permissions are required on the file, not ownership
warning: The 'Dockerfile' contains the 'chown' flag
┌─ images/hive-metastore/Dockerfile:30:1
│
30 │ COPY --from=downloader --chown=0:0 /tmp/libs/*.jar /opt/hive/lib/
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
│
= Chown Flag Exists
= It is considered a best practice for every executable in a container to be owned by the root user even if it is executed by a non-root user, only execution permissions are required on the file, not ownership
warning: 2 warnings emitted
⚠️ MARKDOWN / markdownlint - 6 errors
images/dsf-bpe-full/CHANGELOG.md:133 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### Description"]
images/dsf-bpe-full/CHANGELOG.md:136 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### Versions:"]
images/dsf-bpe-full/CHANGELOG.md:136:13 MD026/no-trailing-punctuation Trailing punctuation in heading [Punctuation: ':']
images/dsf-bpe-full/CHANGELOG.md:137 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "* DFN CA certificate chain fro..."]
images/dsf-bpe-full/CHANGELOG.md:143:31 MD039/no-space-in-links Spaces inside link text [Context: "["MII Data Transfer" process ]"]
images/dsf-bpe-full/CHANGELOG.md:144:30 MD039/no-space-in-links Spaces inside link text [Context: "["MII Data Sharing" process ]"]
⚠️ REPOSITORY / trivy - 8 errors
error: Package: glob
Installed Version: 10.4.5
Vulnerability CVE-2025-64756
Severity: HIGH
Fixed Version: 11.1.0, 10.5.0
Link: [CVE-2025-64756](https://avd.aquasec.com/nvd/cve-2025-64756)
┌─ images/semantic-release/package-lock.json:4800:1
│
4800 │ ╭ "node_modules/npm/node_modules/node-gyp/node_modules/glob": {
4801 │ │ "version": "10.4.5",
4802 │ │ "inBundle": true,
4803 │ │ "license": "ISC",
· │
4817 │ │ }
4818 │ │ },
│ ╰^
│
= glob: glob: Command Injection Vulnerability via Malicious Filenames
= Glob matches files using patterns the shell uses. Starting in version 10.2.0 and prior to versions 10.5.0 and 11.1.0, the glob CLI contains a command injection vulnerability in its -c/--cmd option that allows arbitrary command execution when processing files with malicious names. When glob -c <command> <patterns> are used, matched filenames are passed to a shell with shell: true, enabling shell metacharacters in filenames to trigger command injection and achieve arbitrary code execution under the user or CI account privileges. This issue has been patched in versions 10.5.0 and 11.1.0.
error: Package: glob
Installed Version: 11.0.3
Vulnerability CVE-2025-64756
Severity: HIGH
Fixed Version: 11.1.0, 10.5.0
Link: [CVE-2025-64756](https://avd.aquasec.com/nvd/cve-2025-64756)
┌─ images/semantic-release/package-lock.json:4202:1
│
4202 │ ╭ "node_modules/npm/node_modules/glob": {
4203 │ │ "version": "11.0.3",
4204 │ │ "inBundle": true,
4205 │ │ "license": "ISC",
· │
4222 │ │ }
4223 │ │ },
│ ╰^
│
= glob: glob: Command Injection Vulnerability via Malicious Filenames
= Glob matches files using patterns the shell uses. Starting in version 10.2.0 and prior to versions 10.5.0 and 11.1.0, the glob CLI contains a command injection vulnerability in its -c/--cmd option that allows arbitrary command execution when processing files with malicious names. When glob -c <command> <patterns> are used, matched filenames are passed to a shell with shell: true, enabling shell metacharacters in filenames to trigger command injection and achieve arbitrary code execution under the user or CI account privileges. This issue has been patched in versions 10.5.0 and 11.1.0.
warning: Package: js-yaml
Installed Version: 4.1.0
Vulnerability CVE-2025-64718
Severity: MEDIUM
Fixed Version: 4.1.1, 3.14.2
Link: [CVE-2025-64718](https://avd.aquasec.com/nvd/cve-2025-64718)
┌─ images/semantic-release/package-lock.json:2874:1
│
2874 │ ╭ "node_modules/js-yaml": {
2875 │ │ "version": "4.1.0",
2876 │ │ "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
2877 │ │ "integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
· │
2884 │ │ }
2885 │ │ },
│ ╰^
│
= js-yaml: js-yaml prototype pollution in merge
= js-yaml is a JavaScript YAML parser and dumper. In js-yaml 4.1.0 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1. Users can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default).
error: Package: tar
Installed Version: 7.5.1
Vulnerability CVE-2026-23745
Severity: HIGH
Fixed Version: 7.5.3
Link: [CVE-2026-23745](https://avd.aquasec.com/nvd/cve-2026-23745)
┌─ images/semantic-release/package-lock.json:5408:1
│
5408 │ ╭ "node_modules/npm/node_modules/tar": {
5409 │ │ "version": "7.5.1",
5410 │ │ "inBundle": true,
5411 │ │ "license": "ISC",
· │
5421 │ │ }
5422 │ │ },
│ ╰^
│
= node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails t ...
= node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3.
warning: Package: tar
Installed Version: 7.5.1
Vulnerability CVE-2025-64118
Severity: MEDIUM
Fixed Version: 7.5.2
Link: [CVE-2025-64118](https://avd.aquasec.com/nvd/cve-2025-64118)
┌─ images/semantic-release/package-lock.json:5408:1
│
5408 │ ╭ "node_modules/npm/node_modules/tar": {
5409 │ │ "version": "7.5.1",
5410 │ │ "inBundle": true,
5411 │ │ "license": "ISC",
· │
5421 │ │ }
5422 │ │ },
│ ╰^
│
= node-tar has a race condition leading to uninitialized memory exposure
= node-tar is a Tar for Node.js. In 7.5.1, using .t (aka .list) with { sync: true } to read tar entry contents returns uninitialized memory contents if tar file was changed on disk to a smaller size while being read. This vulnerability is fixed in 7.5.2.
error: Artifact: images/apache-superset/Dockerfile
Type: dockerfile
Vulnerability DS017
Severity: HIGH
Message: The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
Link: [DS017](https://avd.aquasec.com/misconfig/ds017)
┌─ images/apache-superset/Dockerfile:8:1
│
8 │ ╭ RUN <<EOF
9 │ │ set -e
10 │ │ apt-get update -y
11 │ │ apt-get install -y --no-install-recommends alien libaio-dev libaio1 unzip wget
· │
16 │ │ rm oracle-instantclient-basic-23.6.0.24.10-1.el9.x86_64.rpm
17 │ │ EOF
│ ╰^
│
= 'RUN <package-manager> update' instruction alone
= The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
error: Artifact: images/coder-base/Dockerfile
Type: dockerfile
Vulnerability DS017
Severity: HIGH
Message: The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
Link: [DS017](https://avd.aquasec.com/misconfig/ds017)
┌─ images/coder-base/Dockerfile:14:1
│
14 │ ╭ RUN <<EOF
15 │ │ apt-get update
16 │ │ xargs -r -a /tmp/setup/packages.txt apt-get install -y --no-install-recommends
17 │ │
· │
27 │ │ useradd coder --create-home --shell=/bin/bash --uid=10001 --user-group
28 │ │ EOF
│ ╰^
│
= 'RUN <package-manager> update' instruction alone
= The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
error: Artifact: images/hive-metastore/Dockerfile
Type: dockerfile
Vulnerability DS017
Severity: HIGH
Message: The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
Link: [DS017](https://avd.aquasec.com/misconfig/ds017)
┌─ images/hive-metastore/Dockerfile:20:1
│
20 │ ╭ RUN <<EOF
21 │ │ chown -R 1000:1000 /opt/hive
22 │ │ apt-get update
23 │ │ apt-get upgrade -y
· │
27 │ │ rm -rf /var/lib/apt/lists/*
28 │ │ EOF
│ ╰^
│
= 'RUN <package-manager> update' instruction alone
= The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
error: Artifact: images/ml-on-fhir/Dockerfile
Type: dockerfile
Vulnerability DS017
Severity: HIGH
Message: The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
Link: [DS017](https://avd.aquasec.com/misconfig/ds017)
┌─ images/ml-on-fhir/Dockerfile:8:1
│
8 │ ╭ RUN <<EOF
9 │ │ apt-get -y update
10 │ │ apt-get install --no-install-recommends -y openjdk-17-jre-headless
11 │ │ rm -rf /var/lib/apt/lists/*
12 │ │ EOF
│ ╰^
│
= 'RUN <package-manager> update' instruction alone
= The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
error: Artifact: images/semantic-release/Dockerfile
Type: dockerfile
Vulnerability DS017
Severity: HIGH
Message: The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
Link: [DS017](https://avd.aquasec.com/misconfig/ds017)
┌─ images/semantic-release/Dockerfile:10:1
│
10 │ ╭ RUN <<EOF
11 │ │ apt-get update
12 │ │ apt-get install --no-install-recommends -y git bash
13 │ │ apt-get clean
14 │ │ rm -rf /var/lib/apt/lists/*
15 │ │ EOF
│ ╰^
│
= 'RUN <package-manager> update' instruction alone
= The instruction 'RUN <package-manager> update' should always be followed by '<package-manager> install' in the same RUN statement.
warning: 2 warnings emitted
error: 8 errors emitted
See detailed reports in MegaLinter artifacts
You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:
- oxsecurity/megalinter/flavors/terraform@v9.2.0 (54 linters)
- oxsecurity/megalinter/flavors/cupcake@v9.2.0 (88 linters)
Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)
- Documentation: Custom Flavors
- Command:
npx mega-linter-runner@9.2.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,DOCKERFILE_HADOLINT,EDITORCONFIG_EDITORCONFIG_CHECKER,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_KICS,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R
renovate
bot
force-pushed
the
renovate/ghcr.io-datasharingframework-bpe-2.x
branch
from
1dbee57 to
b9682b8
Compare
renovate
bot
force-pushed
the
renovate/ghcr.io-datasharingframework-bpe-2.x
branch
from
b9682b8 to
37167d7
Compare
Trivy image scan report
|
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
gpgv |
CVE-2025-68973 | HIGH | 2.2.27-3ubuntu2.4 | 2.2.27-3ubuntu2.5 |
libpng16-16 |
CVE-2025-64505 | MEDIUM | 1.6.37-3build5 | 1.6.37-3ubuntu0.1 |
libpng16-16 |
CVE-2025-64506 | MEDIUM | 1.6.37-3build5 | 1.6.37-3ubuntu0.1 |
libpng16-16 |
CVE-2025-64720 | MEDIUM | 1.6.37-3build5 | 1.6.37-3ubuntu0.1 |
libpng16-16 |
CVE-2025-65018 | MEDIUM | 1.6.37-3build5 | 1.6.37-3ubuntu0.1 |
libpng16-16 |
CVE-2025-66293 | MEDIUM | 1.6.37-3build5 | 1.6.37-3ubuntu0.3 |
libpng16-16 |
CVE-2026-22695 | MEDIUM | 1.6.37-3build5 | 1.6.37-3ubuntu0.3 |
libpng16-16 |
CVE-2026-22801 | MEDIUM | 1.6.37-3build5 | 1.6.37-3ubuntu0.3 |
libtasn1-6 |
CVE-2025-13151 | MEDIUM | 4.18.0-4ubuntu0.1 | 4.18.0-4ubuntu0.2 |
libtasn1-6 |
CVE-2021-46848 | LOW | 4.18.0-4ubuntu0.1 | 4.18.0-4ubuntu0.2 |
No Misconfigurations found
Java
32 known vulnerabilities found (CRITICAL: 9 HIGH: 17 MEDIUM: 5 LOW: 1)
Show detailed table of vulnerabilities
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
ca.uhn.hapi.fhir:org.hl7.fhir.convertors |
CVE-2023-24057 | CRITICAL | 5.1.0 | 5.6.92 |
ca.uhn.hapi.fhir:org.hl7.fhir.convertors |
CVE-2023-28465 | HIGH | 5.1.0 | 5.6.106 |
ca.uhn.hapi.fhir:org.hl7.fhir.convertors |
CVE-2024-51132 | HIGH | 5.1.0 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.r4 |
CVE-2024-45294 | HIGH | 5.1.0 | 6.3.23 |
ca.uhn.hapi.fhir:org.hl7.fhir.r4 |
CVE-2024-51132 | HIGH | 5.1.0 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.r4 |
CVE-2024-52007 | HIGH | 5.1.0 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.r5 |
CVE-2023-24057 | CRITICAL | 5.1.0 | 5.6.92 |
ca.uhn.hapi.fhir:org.hl7.fhir.r5 |
CVE-2023-28465 | HIGH | 5.1.0 | 5.6.106 |
ca.uhn.hapi.fhir:org.hl7.fhir.r5 |
CVE-2024-45294 | HIGH | 5.1.0 | 6.3.23 |
ca.uhn.hapi.fhir:org.hl7.fhir.r5 |
CVE-2024-51132 | HIGH | 5.1.0 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.r5 |
CVE-2024-52007 | HIGH | 5.1.0 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.utilities |
CVE-2023-24057 | CRITICAL | 5.1.0 | 5.6.92 |
ca.uhn.hapi.fhir:org.hl7.fhir.utilities |
CVE-2023-28465 | HIGH | 5.1.0 | 5.6.106 |
ca.uhn.hapi.fhir:org.hl7.fhir.utilities |
CVE-2024-45294 | HIGH | 5.1.0 | 6.3.23 |
ca.uhn.hapi.fhir:org.hl7.fhir.utilities |
CVE-2024-51132 | HIGH | 5.1.0 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.utilities |
CVE-2024-52007 | HIGH | 5.1.0 | 6.4.0 |
ca.uhn.hapi.fhir:org.hl7.fhir.validation |
CVE-2023-24057 | CRITICAL | 5.1.0 | 5.6.92 |
ca.uhn.hapi.fhir:org.hl7.fhir.validation |
CVE-2023-28465 | HIGH | 5.1.0 | 5.6.106 |
ca.uhn.hapi.fhir:org.hl7.fhir.validation |
CVE-2024-51132 | HIGH | 5.1.0 | 6.4.0 |
com.google.guava:guava |
CVE-2023-2976 | MEDIUM | 29.0-jre | 32.0.0-android |
com.google.guava:guava |
CVE-2020-8908 | LOW | 29.0-jre | 32.0.0-android |
com.nimbusds:nimbus-jose-jwt |
CVE-2025-53864 | MEDIUM | 9.37.3 | 10.0.2, 9.37.4 |
net.minidev:json-smart |
CVE-2024-57699 | HIGH | 2.5.1 | 2.5.2 |
org.apache.commons:commons-lang3 |
CVE-2025-48924 | MEDIUM | 3.9 | 3.18.0 |
org.apache.commons:commons-text |
CVE-2022-42889 | CRITICAL | 1.7 | 1.10.0 |
org.apache.httpcomponents:httpclient |
CVE-2020-13956 | MEDIUM | 4.5.12 | 4.5.13, 5.0.3 |
org.apache.logging.log4j:log4j-core |
CVE-2025-68161 | MEDIUM | 2.25.2 | 2.25.3 |
org.apache.tika:tika-core |
CVE-2025-66516 | CRITICAL | 2.9.2 | 3.2.2 |
org.apache.tika:tika-core |
CVE-2025-66516 | CRITICAL | 2.9.2 | 3.2.2 |
org.apache.tika:tika-core |
CVE-2025-66516 | CRITICAL | 2.9.2 | 3.2.2 |
org.apache.tika:tika-core |
CVE-2025-66516 | CRITICAL | 2.9.2 | 3.2.2 |
org.fhir:ucum |
CVE-2024-55887 | HIGH | 1.0.2 | 1.0.9 |
No Misconfigurations found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.9.0→2.0.1Release Notes
datasharingframework/dsf (ghcr.io/datasharingframework/bpe)
v2.0.1: 2.0.1 - Maintenance ReleaseCompare Source
General remarks:
Bug Fixes:
keyEnciphermentextension, resulted in aFirst certificate from '...' not a client certificateerror (#405). The requirement for thekeyEnciphermentextension was removed with this release.Docker images for this release can be accessed via the GitHub Docker registry - ghcr.io:
Process Plugin API v1 on Maven Central:
Process Plugin API v2 on Maven Central:
DSF Maven Plugin on Maven Central:
Issues closed:
This release contains contributions from @hhund and @schwzr.
v2.0.0: 2.0.0 - Major ReleaseCompare Source
General remarks:
Feature Summary:
TaskandQuestionnaireResponseresources. Internal optimizations improve performance forBinaryresources with a new size limit of resources constraint by PostgreSQL's 4TB limit of Large Objects (limits of forwarding- and reverse-proxies for uploads may be smaller).Docker images for this release can be accessed via the GitHub Docker registry - ghcr.io:
Process Plugin API v1 on Maven Central:
Process Plugin API v2 on Maven Central:
DSF Maven Plugin on Maven Central:
Issues closed:
This release contains contributions from @alexanderkiel, @EmteZogaf, @hhund, @jaboehri, @MadMax93, @schwzr and @wetret.
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.