Skip to content

Document and suppress Trivy issues 652-657 (libssl3t64, stdlib, unknown)#659

Merged
tomwillis608 merged 3 commits into
mainfrom
copilot/fix-cve-2026-31789-libssl3t64
May 6, 2026
Merged

Document and suppress Trivy issues 652-657 (libssl3t64, stdlib, unknown)#659
tomwillis608 merged 3 commits into
mainfrom
copilot/fix-cve-2026-31789-libssl3t64

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 3, 2026

Trivy flagged CVE-2026-31789 (CRITICAL) in libssl3t64 within the app container. The fixed version is 3.5.4-1~deb13u2, already applied during image build via apt-get upgrade -y.

Additional Trivy findings for issues 653–657 were also handled (unknown package CVEs and a Go stdlib CVE reported against the gh binary).

Closes: #653
Closes: #654
Closes: #655
Closes: #656
Closes: #657

# Mitigated: libssl3t64 OpenSSL Vulnerability (CVE-2026-31789)
# ... upgrades libssl3t64 to 3.5.4-1~deb13u2 or later.
CVE-2026-31789
# Accepted Risk: Unknown vulnerability in app container (CVE-2026-32283)
CVE-2026-32283
# Accepted Risk: Unknown vulnerability in app container (CVE-2026-28387)
CVE-2026-28387
# Accepted Risk: Unknown vulnerability in app container (CVE-2026-28388)
CVE-2026-28388
# Accepted Risk: Unknown vulnerability in app container (CVE-2026-28389)
CVE-2026-28389
# Accepted Risk: Go stdlib vulnerability in app container (CVE-2026-32281)
CVE-2026-32281

Summary by Sourcery

Document and formally triage recent Trivy-detected CVEs in the app container, and align scanner suppression with the documented risk decisions.

Enhancements:

  • Extend the threat model with detailed analyses, risk assessments, and mitigation strategies for new Trivy-reported CVEs affecting the app container (unknown packages), Go stdlib in the GitHub CLI binary, and libssl3t64 in the base image.

Chores:

  • Update .trivyignore to suppress the newly documented CVEs with rationale and acceptance dates so that CI noise matches the recorded risk posture.

Copilot AI linked an issue May 3, 2026 that may be closed by this pull request
6 tasks
@tomwillis608
Copy link
Copy Markdown
Member

@copilot - handle all issues 652 through 657 in this PR

Agent-Logs-Url: https://github.com/sett-and-hive/sarif-to-comment-action/sessions/23db64fc-7456-45be-a3c1-60e8704fa4eb

Co-authored-by: tomwillis608 <15950648+tomwillis608@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

Testing script results from test/test.sh
✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes

Test script outputs from test/test.sh

Convert SARIF file ./test/fixtures/codeql.sarif
DryRun results:
owner: sett-and-hive
repo: sarif-to-comment-action
issue: #1
title: Test security PR comment from build
body: # Test security PR comment from build

Results

Suppressed Results

Nothing here.

Rules information

Rules details
- js/xss [error] 

> Client-side cross-site scripting
Details
{
    "driver": {
        "name": "CodeQL command-line toolchain",
        "organization": "GitHub",
        "semanticVersion": "2.2.4",
        "rules": [
            {
                "id": "js/xss",
                "name": "js/xss",
                "shortDescription": {
                    "text": "Client-side cross-site scripting"
                },
                "fullDescription": {
                    "text": "Writing user input directly to the DOM allows for a cross-site scripting vulnerability."
                },
                "defaultConfiguration": {
                    "level": "error"
                },
                "properties": {
                    "tags": [
                        "security",
                        "external/cwe/cwe-079",
                        "external/cwe/cwe-116"
                    ],
                    "kind": "path-problem",
                    "precision": "high",
                    "name": "Client-side cross-site scripting",
                    "description": "Writing user input directly to the DOM allows for\n              a cross-site scripting vulnerability.",
                    "id": "js/xss",
                    "problem.severity": "error"
                }
            }
        ]
    }
}

Tool information

  • Name: CodeQL command-line toolchain
  • Organization: GitHub
  • Version: 2.2.4

(node:30) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Some comments were not posted, reasons will be included
This is a dry run
RC = 0
Convert SARIF file ./test/fixtures/odc.sarif
DryRun results:
owner: sett-and-hive
repo: sarif-to-comment-action
issue: #1
title: Test security PR comment from build
body: # Test security PR comment from build

Results

  • [ERROR] [CVE-2022-24823] CVE-2022-24823 - Netty is an open-source, asynchronous event-driven network application framework. The package io.netty:netty-codec-httpprior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's ownjava.io.tmpdir when starting the JVM or use DefaultHttpDataFactory.setBaseDir\(...\) to set the directory to something that is only readable by the current user.

Suppressed Results

Nothing here.

Rules information

Rules details
- CVE-2022-24823 [undefined] 

> Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final
Details
{
    "driver": {
        "name": "dependency-check",
        "version": "7.1.0",
        "informationUri": "https://jeremylong.github.io/DependencyCheck/",
        "rules": [
            {
                "id": "CVE-2022-24823",
                "shortDescription": {
                    "text": "Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final"
                },
                "fullDescription": {
                    "text": "Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user."
                },
                "help": {
                    "text": "",
                    "markdown": "For more information see [CVE-2022-24823](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24823).\n\n\nIf this is a false positive - consider using the HTML report to generate a suppression file. For more information see [How dependency-check works](https://jeremylong.github.io/DependencyCheck/general/internals.html), [How to read the HTML report](https://jeremylong.github.io/DependencyCheck/general/thereport.html), and [Suppressing false positives](https://jeremylong.github.io/DependencyCheck/general/suppression.html)."
                },
                "properties": {
                    "cvssv2_score": 1.9,
                    "cvssv2_accessVector": "LOCAL",
                    "cvssv2_accessComplexity": "MEDIUM",
                    "cvssv2_authenticationr": "NONE",
                    "cvssv2_confidentialImpact": "$enc.json($rule.cvssv2ConfidentialityImpact)",
                    "cvssv2_integrityImpact": "NONE",
                    "cvssv2_availabilityImpact": "NONE",
                    "cvssv2_severity": "LOW",
                    "cvssv3_baseScore": 5.5,
                    "cvssv3_attackVector": "LOCAL",
                    "cvssv3_attackComplexity": "LOW",
                    "cvssv3_privilegesRequired": "LOW",
                    "cvssv3_userInteraction": "NONE",
                    "cvssv3_scope": "UNCHANGED",
                    "cvssv3_confidentialityImpact": "HIGH",
                    "cvssv3_integrityImpact": "NONE",
                    "cvssv3_availabilityImpact": "NONE",
                    "cvssv3_baseSeverity": "MEDIUM",
                    "cvssv3_exploitabilityScore": "1.8",
                    "cvssv3_impactScore": "3.6",
                    "cvssv3_version": "3.1",
                    "source": "NVD"
                },
                "defaultConfiguration": {
                    "level": "error"
                }
            }
        ],
        "properties": {
            "disclaimer": "Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user's risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.",
            "nvd": "This report contains data retrieved from the National Vulnerability Database: http://nvd.nist.gov",
            "npm": "This report may contain data retrieved from the NPM Public Advisories: https://www.npmjs.com/advisories",
            "retirejs": "This report may contain data retrieved from the RetireJS community: https://retirejs.github.io/retire.js/",
            "ossindex": "This report may contain data retrieved from the Sonatype OSS Index: https://ossindex.sonatype.org",
            "NVD CVE Checked": "2022-05-25T15:58:07",
            "NVD CVE Modified": "2022-05-25T14:00:01",
            "VersionCheckOn": "2022-05-25T15:58:07"
        }
    }
}

Tool information

  • Name: dependency-check
  • Organization: undefined
  • Version: undefined

(node:32) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Some comments were not posted, reasons will be included
This is a dry run
RC = 0
ERROR: Bad JSON in ./test/fixtures/zero-byte.sarif
ERROR: No SARIF file found at ./test/fixtures/sir-not-appearing-in-thisfilm.sarif
jq: parse error: Unfinished string at EOF at line 2, column 0
ERROR: Bad JSON in ./test/fixtures/bad-json.sarif
jq: error (at ./test/fixtures/short.sarif:1): Cannot iterate over null (null)

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

PR smoke test of comment with security scanning results

Results

  • [ERROR] [CVE-2022-24823] CVE-2022-24823 - Netty is an open-source, asynchronous event-driven network application framework. The package io.netty:netty-codec-httpprior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's ownjava.io.tmpdir when starting the JVM or use DefaultHttpDataFactory.setBaseDir\(...\) to set the directory to something that is only readable by the current user.

Suppressed Results

Nothing here.

Rules information

Rules details
- CVE-2022-24823 [undefined] 

> Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final
Details
{
    "driver": {
        "name": "dependency-check",
        "version": "7.1.0",
        "informationUri": "https://jeremylong.github.io/DependencyCheck/",
        "rules": [
            {
                "id": "CVE-2022-24823",
                "shortDescription": {
                    "text": "Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final"
                },
                "fullDescription": {
                    "text": "Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user."
                },
                "help": {
                    "text": "",
                    "markdown": "For more information see [CVE-2022-24823](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24823).\n\n\nIf this is a false positive - consider using the HTML report to generate a suppression file. For more information see [How dependency-check works](https://jeremylong.github.io/DependencyCheck/general/internals.html), [How to read the HTML report](https://jeremylong.github.io/DependencyCheck/general/thereport.html), and [Suppressing false positives](https://jeremylong.github.io/DependencyCheck/general/suppression.html)."
                },
                "properties": {
                    "cvssv2_score": 1.9,
                    "cvssv2_accessVector": "LOCAL",
                    "cvssv2_accessComplexity": "MEDIUM",
                    "cvssv2_authenticationr": "NONE",
                    "cvssv2_confidentialImpact": "$enc.json($rule.cvssv2ConfidentialityImpact)",
                    "cvssv2_integrityImpact": "NONE",
                    "cvssv2_availabilityImpact": "NONE",
                    "cvssv2_severity": "LOW",
                    "cvssv3_baseScore": 5.5,
                    "cvssv3_attackVector": "LOCAL",
                    "cvssv3_attackComplexity": "LOW",
                    "cvssv3_privilegesRequired": "LOW",
                    "cvssv3_userInteraction": "NONE",
                    "cvssv3_scope": "UNCHANGED",
                    "cvssv3_confidentialityImpact": "HIGH",
                    "cvssv3_integrityImpact": "NONE",
                    "cvssv3_availabilityImpact": "NONE",
                    "cvssv3_baseSeverity": "MEDIUM",
                    "cvssv3_exploitabilityScore": "1.8",
                    "cvssv3_impactScore": "3.6",
                    "cvssv3_version": "3.1",
                    "source": "NVD"
                },
                "defaultConfiguration": {
                    "level": "error"
                }
            }
        ],
        "properties": {
            "disclaimer": "Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user's risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.",
            "nvd": "This report contains data retrieved from the National Vulnerability Database: http://nvd.nist.gov",
            "npm": "This report may contain data retrieved from the NPM Public Advisories: https://www.npmjs.com/advisories",
            "retirejs": "This report may contain data retrieved from the RetireJS community: https://retirejs.github.io/retire.js/",
            "ossindex": "This report may contain data retrieved from the Sonatype OSS Index: https://ossindex.sonatype.org",
            "NVD CVE Checked": "2022-05-25T15:58:07",
            "NVD CVE Modified": "2022-05-25T14:00:01",
            "VersionCheckOn": "2022-05-25T15:58:07"
        }
    }
}

Tool information

  • Name: dependency-check
  • Organization: undefined
  • Version: undefined

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

🛡️ Trivy Scan Report

🔧 Config Scan: ✅ Clean

🐳 Image Scan: ✅ Clean

Copilot AI changed the title [WIP] Fix security vulnerability CVE-2026-31789 in libssl3t64 Document and suppress CVE-2026-31789 for libssl3t64 May 3, 2026
Copilot AI requested a review from tomwillis608 May 3, 2026 20:14
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

Testing script results from test/test.sh
❌ Test result: fails%0A❌ Test result: fails%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes

Test script outputs from test/test.sh

docker: invalid reference format

Run 'docker run --help' for more information
docker: invalid reference format

Run 'docker run --help' for more information
docker: invalid reference format

Run 'docker run --help' for more information
docker: invalid reference format

Run 'docker run --help' for more information
docker: invalid reference format

Run 'docker run --help' for more information
docker: invalid reference format

Run 'docker run --help' for more information

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

PR smoke test of comment with security scanning results

Results

  • [ERROR] [CVE-2022-24823] CVE-2022-24823 - Netty is an open-source, asynchronous event-driven network application framework. The package io.netty:netty-codec-httpprior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's ownjava.io.tmpdir when starting the JVM or use DefaultHttpDataFactory.setBaseDir\(...\) to set the directory to something that is only readable by the current user.

Suppressed Results

Nothing here.

Rules information

Rules details
- CVE-2022-24823 [undefined] 

> Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final
Details
{
    "driver": {
        "name": "dependency-check",
        "version": "7.1.0",
        "informationUri": "https://jeremylong.github.io/DependencyCheck/",
        "rules": [
            {
                "id": "CVE-2022-24823",
                "shortDescription": {
                    "text": "Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final"
                },
                "fullDescription": {
                    "text": "Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user."
                },
                "help": {
                    "text": "",
                    "markdown": "For more information see [CVE-2022-24823](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24823).\n\n\nIf this is a false positive - consider using the HTML report to generate a suppression file. For more information see [How dependency-check works](https://jeremylong.github.io/DependencyCheck/general/internals.html), [How to read the HTML report](https://jeremylong.github.io/DependencyCheck/general/thereport.html), and [Suppressing false positives](https://jeremylong.github.io/DependencyCheck/general/suppression.html)."
                },
                "properties": {
                    "cvssv2_score": 1.9,
                    "cvssv2_accessVector": "LOCAL",
                    "cvssv2_accessComplexity": "MEDIUM",
                    "cvssv2_authenticationr": "NONE",
                    "cvssv2_confidentialImpact": "$enc.json($rule.cvssv2ConfidentialityImpact)",
                    "cvssv2_integrityImpact": "NONE",
                    "cvssv2_availabilityImpact": "NONE",
                    "cvssv2_severity": "LOW",
                    "cvssv3_baseScore": 5.5,
                    "cvssv3_attackVector": "LOCAL",
                    "cvssv3_attackComplexity": "LOW",
                    "cvssv3_privilegesRequired": "LOW",
                    "cvssv3_userInteraction": "NONE",
                    "cvssv3_scope": "UNCHANGED",
                    "cvssv3_confidentialityImpact": "HIGH",
                    "cvssv3_integrityImpact": "NONE",
                    "cvssv3_availabilityImpact": "NONE",
                    "cvssv3_baseSeverity": "MEDIUM",
                    "cvssv3_exploitabilityScore": "1.8",
                    "cvssv3_impactScore": "3.6",
                    "cvssv3_version": "3.1",
                    "source": "NVD"
                },
                "defaultConfiguration": {
                    "level": "error"
                }
            }
        ],
        "properties": {
            "disclaimer": "Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user's risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.",
            "nvd": "This report contains data retrieved from the National Vulnerability Database: http://nvd.nist.gov",
            "npm": "This report may contain data retrieved from the NPM Public Advisories: https://www.npmjs.com/advisories",
            "retirejs": "This report may contain data retrieved from the RetireJS community: https://retirejs.github.io/retire.js/",
            "ossindex": "This report may contain data retrieved from the Sonatype OSS Index: https://ossindex.sonatype.org",
            "NVD CVE Checked": "2022-05-25T15:58:07",
            "NVD CVE Modified": "2022-05-25T14:00:01",
            "VersionCheckOn": "2022-05-25T15:58:07"
        }
    }
}

Tool information

  • Name: dependency-check
  • Organization: undefined
  • Version: undefined

Agent-Logs-Url: https://github.com/sett-and-hive/sarif-to-comment-action/sessions/9c8ccbcb-bf51-4873-ba12-e4a450558605

Co-authored-by: tomwillis608 <15950648+tomwillis608@users.noreply.github.com>
@tomwillis608
Copy link
Copy Markdown
Member

@copilot explain the failures reported in the CI bash testing:

Testing script results from test/test.sh
❌ Test result: fails%0A❌ Test result: fails%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes

Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 3, 2026

@copilot - handle all issues 652 through 657 in this PR

Handled issues 653–657 by documenting CVEs and adding .trivyignore suppressions (commit 9995b3a).

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

PR smoke test of comment with security scanning results

Results

  • [ERROR] [CVE-2022-24823] CVE-2022-24823 - Netty is an open-source, asynchronous event-driven network application framework. The package io.netty:netty-codec-httpprior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's ownjava.io.tmpdir when starting the JVM or use DefaultHttpDataFactory.setBaseDir\(...\) to set the directory to something that is only readable by the current user.

Suppressed Results

Nothing here.

Rules information

Rules details
- CVE-2022-24823 [undefined] 

> Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final
Details
{
    "driver": {
        "name": "dependency-check",
        "version": "7.1.0",
        "informationUri": "https://jeremylong.github.io/DependencyCheck/",
        "rules": [
            {
                "id": "CVE-2022-24823",
                "shortDescription": {
                    "text": "Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final"
                },
                "fullDescription": {
                    "text": "Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user."
                },
                "help": {
                    "text": "",
                    "markdown": "For more information see [CVE-2022-24823](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24823).\n\n\nIf this is a false positive - consider using the HTML report to generate a suppression file. For more information see [How dependency-check works](https://jeremylong.github.io/DependencyCheck/general/internals.html), [How to read the HTML report](https://jeremylong.github.io/DependencyCheck/general/thereport.html), and [Suppressing false positives](https://jeremylong.github.io/DependencyCheck/general/suppression.html)."
                },
                "properties": {
                    "cvssv2_score": 1.9,
                    "cvssv2_accessVector": "LOCAL",
                    "cvssv2_accessComplexity": "MEDIUM",
                    "cvssv2_authenticationr": "NONE",
                    "cvssv2_confidentialImpact": "$enc.json($rule.cvssv2ConfidentialityImpact)",
                    "cvssv2_integrityImpact": "NONE",
                    "cvssv2_availabilityImpact": "NONE",
                    "cvssv2_severity": "LOW",
                    "cvssv3_baseScore": 5.5,
                    "cvssv3_attackVector": "LOCAL",
                    "cvssv3_attackComplexity": "LOW",
                    "cvssv3_privilegesRequired": "LOW",
                    "cvssv3_userInteraction": "NONE",
                    "cvssv3_scope": "UNCHANGED",
                    "cvssv3_confidentialityImpact": "HIGH",
                    "cvssv3_integrityImpact": "NONE",
                    "cvssv3_availabilityImpact": "NONE",
                    "cvssv3_baseSeverity": "MEDIUM",
                    "cvssv3_exploitabilityScore": "1.8",
                    "cvssv3_impactScore": "3.6",
                    "cvssv3_version": "3.1",
                    "source": "NVD"
                },
                "defaultConfiguration": {
                    "level": "error"
                }
            }
        ],
        "properties": {
            "disclaimer": "Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user's risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.",
            "nvd": "This report contains data retrieved from the National Vulnerability Database: http://nvd.nist.gov",
            "npm": "This report may contain data retrieved from the NPM Public Advisories: https://www.npmjs.com/advisories",
            "retirejs": "This report may contain data retrieved from the RetireJS community: https://retirejs.github.io/retire.js/",
            "ossindex": "This report may contain data retrieved from the Sonatype OSS Index: https://ossindex.sonatype.org",
            "NVD CVE Checked": "2022-05-25T15:58:07",
            "NVD CVE Modified": "2022-05-25T14:00:01",
            "VersionCheckOn": "2022-05-25T15:58:07"
        }
    }
}

Tool information

  • Name: dependency-check
  • Organization: undefined
  • Version: undefined

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

Testing script results from test/test.sh
✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes%0A✅ Test result: passes

Test script outputs from test/test.sh

Convert SARIF file ./test/fixtures/codeql.sarif
DryRun results:
owner: sett-and-hive
repo: sarif-to-comment-action
issue: #1
title: Test security PR comment from build
body: # Test security PR comment from build

Results

Suppressed Results

Nothing here.

Rules information

Rules details
- js/xss [error] 

> Client-side cross-site scripting
Details
{
    "driver": {
        "name": "CodeQL command-line toolchain",
        "organization": "GitHub",
        "semanticVersion": "2.2.4",
        "rules": [
            {
                "id": "js/xss",
                "name": "js/xss",
                "shortDescription": {
                    "text": "Client-side cross-site scripting"
                },
                "fullDescription": {
                    "text": "Writing user input directly to the DOM allows for a cross-site scripting vulnerability."
                },
                "defaultConfiguration": {
                    "level": "error"
                },
                "properties": {
                    "tags": [
                        "security",
                        "external/cwe/cwe-079",
                        "external/cwe/cwe-116"
                    ],
                    "kind": "path-problem",
                    "precision": "high",
                    "name": "Client-side cross-site scripting",
                    "description": "Writing user input directly to the DOM allows for\n              a cross-site scripting vulnerability.",
                    "id": "js/xss",
                    "problem.severity": "error"
                }
            }
        ]
    }
}

Tool information

  • Name: CodeQL command-line toolchain
  • Organization: GitHub
  • Version: 2.2.4

(node:30) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Some comments were not posted, reasons will be included
This is a dry run
RC = 0
Convert SARIF file ./test/fixtures/odc.sarif
DryRun results:
owner: sett-and-hive
repo: sarif-to-comment-action
issue: #1
title: Test security PR comment from build
body: # Test security PR comment from build

Results

  • [ERROR] [CVE-2022-24823] CVE-2022-24823 - Netty is an open-source, asynchronous event-driven network application framework. The package io.netty:netty-codec-httpprior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's ownjava.io.tmpdir when starting the JVM or use DefaultHttpDataFactory.setBaseDir\(...\) to set the directory to something that is only readable by the current user.

Suppressed Results

Nothing here.

Rules information

Rules details
- CVE-2022-24823 [undefined] 

> Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final
Details
{
    "driver": {
        "name": "dependency-check",
        "version": "7.1.0",
        "informationUri": "https://jeremylong.github.io/DependencyCheck/",
        "rules": [
            {
                "id": "CVE-2022-24823",
                "shortDescription": {
                    "text": "Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final"
                },
                "fullDescription": {
                    "text": "Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user."
                },
                "help": {
                    "text": "",
                    "markdown": "For more information see [CVE-2022-24823](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24823).\n\n\nIf this is a false positive - consider using the HTML report to generate a suppression file. For more information see [How dependency-check works](https://jeremylong.github.io/DependencyCheck/general/internals.html), [How to read the HTML report](https://jeremylong.github.io/DependencyCheck/general/thereport.html), and [Suppressing false positives](https://jeremylong.github.io/DependencyCheck/general/suppression.html)."
                },
                "properties": {
                    "cvssv2_score": 1.9,
                    "cvssv2_accessVector": "LOCAL",
                    "cvssv2_accessComplexity": "MEDIUM",
                    "cvssv2_authenticationr": "NONE",
                    "cvssv2_confidentialImpact": "$enc.json($rule.cvssv2ConfidentialityImpact)",
                    "cvssv2_integrityImpact": "NONE",
                    "cvssv2_availabilityImpact": "NONE",
                    "cvssv2_severity": "LOW",
                    "cvssv3_baseScore": 5.5,
                    "cvssv3_attackVector": "LOCAL",
                    "cvssv3_attackComplexity": "LOW",
                    "cvssv3_privilegesRequired": "LOW",
                    "cvssv3_userInteraction": "NONE",
                    "cvssv3_scope": "UNCHANGED",
                    "cvssv3_confidentialityImpact": "HIGH",
                    "cvssv3_integrityImpact": "NONE",
                    "cvssv3_availabilityImpact": "NONE",
                    "cvssv3_baseSeverity": "MEDIUM",
                    "cvssv3_exploitabilityScore": "1.8",
                    "cvssv3_impactScore": "3.6",
                    "cvssv3_version": "3.1",
                    "source": "NVD"
                },
                "defaultConfiguration": {
                    "level": "error"
                }
            }
        ],
        "properties": {
            "disclaimer": "Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user's risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.",
            "nvd": "This report contains data retrieved from the National Vulnerability Database: http://nvd.nist.gov",
            "npm": "This report may contain data retrieved from the NPM Public Advisories: https://www.npmjs.com/advisories",
            "retirejs": "This report may contain data retrieved from the RetireJS community: https://retirejs.github.io/retire.js/",
            "ossindex": "This report may contain data retrieved from the Sonatype OSS Index: https://ossindex.sonatype.org",
            "NVD CVE Checked": "2022-05-25T15:58:07",
            "NVD CVE Modified": "2022-05-25T14:00:01",
            "VersionCheckOn": "2022-05-25T15:58:07"
        }
    }
}

Tool information

  • Name: dependency-check
  • Organization: undefined
  • Version: undefined

(node:32) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Some comments were not posted, reasons will be included
This is a dry run
RC = 0
ERROR: Bad JSON in ./test/fixtures/zero-byte.sarif
ERROR: No SARIF file found at ./test/fixtures/sir-not-appearing-in-thisfilm.sarif
jq: parse error: Unfinished string at EOF at line 2, column 0
ERROR: Bad JSON in ./test/fixtures/bad-json.sarif
jq: error (at ./test/fixtures/short.sarif:1): Cannot iterate over null (null)

Copilot AI changed the title Document and suppress CVE-2026-31789 for libssl3t64 Document and suppress Trivy issues 652-657 (libssl3t64, stdlib, unknown) May 3, 2026
Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 3, 2026

@copilot explain the failures reported in the CI bash testing:

...

The CI comment is produced by .github/workflows/ci-test.yamltest/test.sh. That script URL‑encodes newlines (%0A at line 126) before writing to GITHUB_OUTPUT, which is why the summary looks like fails%0A.... The first two entries in that summary are the CodeQL and ODC fixture runs (lines 95–101); they show when run_docker exits non‑zero or when the output file doesn’t contain the exact ## Results line. Because each run_test is invoked via command substitution (pass=$(run_test ...)), any exit inside test_result only terminates the subshell, so the workflow continues and can still succeed. In the latest CI run for this PR (run 25289680044, attempt 2), the logs show all passes; the fails output likely came from an earlier attempt/run where the container exited non‑zero (commonly when the CLI tries to use the fake token and returns HttpError: Bad credentials). No UI changes were made.

@tomwillis608 tomwillis608 marked this pull request as ready for review May 6, 2026 11:57
@tomwillis608 tomwillis608 merged commit a87496e into main May 6, 2026
8 checks passed
@tomwillis608 tomwillis608 deleted the copilot/fix-cve-2026-31789-libssl3t64 branch May 6, 2026 11:57
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented May 6, 2026

Reviewer's Guide

Documents and formally accepts/mitigates several new Trivy-reported CVEs in the threat model and suppresses them in Trivy, aligning justification and acceptance metadata across both docs and scanner config.

Sequence diagram for Trivy scan with new CVE suppressions

sequenceDiagram
    participant Dev as Developer
    participant CI as CI_pipeline
    participant Trivy as Trivy_scanner
    participant Ignore as trivyignore_config
    participant Threat as Threat_model_docs

    Dev->>Threat: Document CVE_2026_31789 CVE_2026_32283 CVE_2026_28387 CVE_2026_28388 CVE_2026_28389 CVE_2026_32281
    Dev->>Ignore: Add CVE IDs with mitigation and acceptance comments

    Dev->>CI: Push changes
    CI->>Trivy: Run container_image_scan
    Trivy->>Ignore: Load ignore_rules

    Trivy->>Trivy: Detect CVE_2026_31789 in libssl3t64
    Trivy->>Ignore: Check CVE_2026_31789 against ignore_rules
    Ignore-->>Trivy: Match_found_with_mitigated_status
    Trivy-->>CI: Report CVE_2026_31789 as suppressed

    Trivy->>Trivy: Detect unknown_package CVE_2026_32283 CVE_2026_28387 CVE_2026_28388 CVE_2026_28389
    Trivy->>Ignore: Check unknown_package_CVEs against ignore_rules
    Ignore-->>Trivy: Match_found_with_accepted_risk
    Trivy-->>CI: Report unknown_package_CVEs as suppressed

    Trivy->>Trivy: Detect Go_stdlib CVE_2026_32281 in gh_binary
    Trivy->>Ignore: Check CVE_2026_32281 against ignore_rules
    Ignore-->>Trivy: Match_found_with_accepted_risk
    Trivy-->>CI: Report CVE_2026_32281 as suppressed

    CI-->>Dev: CI_passes_without_new_blocking_vulnerabilities
Loading

Flow diagram for CVE triage and Trivy suppression strategy

flowchart TD
    A[Trivy reports CVE in app container] --> B[Identify CVE ID and affected component]
    B --> C{Is affected package and fixed version known?}

    C -->|Yes: system package libssl3t64| D[Verify Dockerfile applies apt-get upgrade -y]
    D --> E{Is image built with fixed libssl3t64 version 3.5.4-1~deb13u2 or later?}
    E -->|Yes| F[Classify as mitigated in final image]
    F --> G[Document mitigation and risk in threat_model]
    G --> H[Add CVE_2026_31789 to trivyignore with mitigated rationale]

    C -->|No: unknown package CVE_2026_32283 28387 28388 28389| I[Assess existing hardening controls in Dockerfile]
    I --> J[Conclude no actionable remediation path yet]
    J --> K[Classify as low_to_unknown risk and temporary accepted risk]
    K --> L[Document analysis and acceptance in threat_model]
    L --> M[Add CVE_2026_32283 28387 28388 28389 to trivyignore as accepted risk]

    C -->|Yes: Go stdlib in gh binary CVE_2026_32281| N[Check upstream GitHub CLI Go version]
    N --> O{Is gh built with fixed Go version 1.25.9+ or 1.26.2+?}
    O -->|No| P[Cannot patch embedded stdlib until upstream gh is rebuilt]
    P --> Q[Evaluate constrained attack surface for gh usage]
    Q --> R[Classify as low_to_medium temporary accepted risk]
    R --> S[Document mitigation strategy and monitoring plan in threat_model]
    S --> T[Add CVE_2026_32281 to trivyignore as temporary accepted risk]

    E -->|No| U[Update Dockerfile or base image to reach fixed libssl3t64]
    U --> V[Rebuild image and rerun Trivy]
    V --> D
Loading

File-Level Changes

Change Details Files
Added detailed threat-model entries for newly discovered Trivy CVEs in the app container, including unknown-package findings and a Go stdlib issue in the GitHub CLI binary.
  • Documented CVE-2026-32283, CVE-2026-28387, CVE-2026-28388, and CVE-2026-28389 as unknown app container vulnerabilities with shared analysis, risk assessment, and mitigation strategy.
  • Documented CVE-2026-32281 as a Go stdlib vulnerability embedded in the pinned GitHub CLI binary, including current Go version, upgrade constraints, and attack surface in this action.
  • Linked each CVE entry to its NVD reference and recorded explicit acceptance dates for the temporary risk exceptions.
docs/threat_model.md
Documented mitigation of the libssl3t64 OpenSSL CVE in the container build process and aligned it with Trivy behavior.
  • Added a threat-model section for CVE-2026-31789 describing the vulnerable libssl3t64 version, the fixed version, and how Debian security updates are applied via apt-get upgrade during Docker build.
  • Explained why Trivy still flags the CVE due to intermediate layers and justified suppression in the context of the final built image.
  • Recorded risk assessment, mitigation strategy, and acceptance date plus references to NVD and Debian Security Tracker.
docs/threat_model.md
Updated Trivy suppression configuration to ignore the newly documented CVEs with inline rationale. .trivyignore

Assessment against linked issues

Issue Objective Addressed Explanation
#652 Document CVE-2026-31789 in docs/threat_model.md under the risk mitigation section, including analysis, mitigation, and acceptance details.
#652 Ensure CVE-2026-31789 is either remediated by using libssl3t64 version 3.5.4-1~deb13u2 or later in the app image, or suppressed in .trivyignore with justification and an acceptance date so that Trivy scans only show fixed/accepted issues.
#652 Update uv.lock with the latest versions of relevant packages if needed as part of addressing this vulnerability.
#653 Document CVE-2026-28387 in the threat model (docs/threat_model.md) under risk mitigation, including analysis, mitigation/acceptance decision, and references.
#653 Ensure CVE-2026-28387 no longer blocks Trivy scans by either upgrading the affected component to a fixed version or adding the CVE to .trivyignore with justification and an acceptance date.
#653 Update dependency metadata (e.g., uv.lock) if a package upgrade is required as part of the remediation for CVE-2026-28387.
#654 Document CVE-2026-28388 in docs/threat_model.md under the Risk Mitigation section, including analysis, risk assessment, mitigation/acceptance, and references.
#654 Ensure Trivy no longer reports CVE-2026-28388 as an unhandled finding by either upgrading the affected package to a fixed version or, if no fix is available, adding CVE-2026-28388 to .trivyignore with justification and an acceptance date.
#654 Update dependencies (including uv.lock) if a fixed version for the package underlying CVE-2026-28388 becomes available and is needed to remediate the vulnerability.
#655 Document CVE-2026-28389 in docs/threat_model.md under the Risk Mitigation section, including analysis, risk assessment, mitigation/acceptance decision, and references.
#655 Ensure CVE-2026-28389 no longer blocks Trivy scans by either upgrading the affected package to a fixed version or adding the CVE to .trivyignore with justification and an acceptance date.
#655 Update dependency locks (e.g., uv.lock) as needed in response to this vulnerability, ensuring packages are at appropriate versions. The PR description and diff do not show any changes to uv.lock or other lockfiles. While the issue states that uv.lock should be updated with the latest package versions as needed, this PR only updates the threat model and Trivy ignore configuration.
#656 Document CVE-2026-32281 in docs/threat_model.md under the Risk Mitigation section, including analysis, risk assessment, mitigation strategy, and references.
#656 Ensure CVE-2026-32281 is either remediated by updating the affected stdlib/Go version to a fixed release or explicitly accepted and suppressed in .trivyignore with justification and an acceptance date so that Trivy scans pass (or only show accepted/ignored vulnerabilities).
#657 Document CVE-2026-32283 in docs/threat_model.md under the Risk Mitigation section, including analysis, mitigation/acceptance, and references.
#657 Either remediate CVE-2026-32283 or explicitly suppress it in .trivyignore with justification and acceptance date so that Trivy scans pass or only show accepted/ignored vulnerabilities.
#657 Update dependencies (including uv.lock) as needed to address CVE-2026-32283, or determine that no dependency update is currently possible or required.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • The four "Unknown App Container Vulnerability" sections (CVE-2026-32283 / 28387 / 28388 / 28389) repeat nearly identical analysis and mitigation text; consider factoring the common rationale into a single shared subsection or table and only highlighting the CVE-specific differences to keep the threat model more maintainable.
  • For CVE-2026-31789, since the mitigation relies on apt-get upgrade -y during build, it may be worth briefly clarifying in the threat model (or Dockerfile comments) whether Trivy is configured to scan the final image only, or if additional build args (e.g., --no-cache) or multi-stage builds could reduce false positives from pre-upgrade layers instead of relying solely on suppression.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The four "Unknown App Container Vulnerability" sections (CVE-2026-32283 / 28387 / 28388 / 28389) repeat nearly identical analysis and mitigation text; consider factoring the common rationale into a single shared subsection or table and only highlighting the CVE-specific differences to keep the threat model more maintainable.
- For CVE-2026-31789, since the mitigation relies on `apt-get upgrade -y` during build, it may be worth briefly clarifying in the threat model (or Dockerfile comments) whether Trivy is configured to scan the final image only, or if additional build args (e.g., `--no-cache`) or multi-stage builds could reduce false positives from pre-upgrade layers instead of relying solely on suppression.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

PR smoke test of comment with security scanning results

Results

  • [ERROR] [CVE-2022-24823] CVE-2022-24823 - Netty is an open-source, asynchronous event-driven network application framework. The package io.netty:netty-codec-httpprior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's ownjava.io.tmpdir when starting the JVM or use DefaultHttpDataFactory.setBaseDir\(...\) to set the directory to something that is only readable by the current user.

Suppressed Results

Nothing here.

Rules information

Rules details
- CVE-2022-24823 [undefined] 

> Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final
Details
{
    "driver": {
        "name": "dependency-check",
        "version": "7.1.0",
        "informationUri": "https://jeremylong.github.io/DependencyCheck/",
        "rules": [
            {
                "id": "CVE-2022-24823",
                "shortDescription": {
                    "text": "Medium severity - CVE-2022-24823 Exposure of Resource to Wrong Sphere vulnerability in pkg:maven/io.netty/netty-transport@4.1.76.Final"
                },
                "fullDescription": {
                    "text": "Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user."
                },
                "help": {
                    "text": "",
                    "markdown": "For more information see [CVE-2022-24823](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24823).\n\n\nIf this is a false positive - consider using the HTML report to generate a suppression file. For more information see [How dependency-check works](https://jeremylong.github.io/DependencyCheck/general/internals.html), [How to read the HTML report](https://jeremylong.github.io/DependencyCheck/general/thereport.html), and [Suppressing false positives](https://jeremylong.github.io/DependencyCheck/general/suppression.html)."
                },
                "properties": {
                    "cvssv2_score": 1.9,
                    "cvssv2_accessVector": "LOCAL",
                    "cvssv2_accessComplexity": "MEDIUM",
                    "cvssv2_authenticationr": "NONE",
                    "cvssv2_confidentialImpact": "$enc.json($rule.cvssv2ConfidentialityImpact)",
                    "cvssv2_integrityImpact": "NONE",
                    "cvssv2_availabilityImpact": "NONE",
                    "cvssv2_severity": "LOW",
                    "cvssv3_baseScore": 5.5,
                    "cvssv3_attackVector": "LOCAL",
                    "cvssv3_attackComplexity": "LOW",
                    "cvssv3_privilegesRequired": "LOW",
                    "cvssv3_userInteraction": "NONE",
                    "cvssv3_scope": "UNCHANGED",
                    "cvssv3_confidentialityImpact": "HIGH",
                    "cvssv3_integrityImpact": "NONE",
                    "cvssv3_availabilityImpact": "NONE",
                    "cvssv3_baseSeverity": "MEDIUM",
                    "cvssv3_exploitabilityScore": "1.8",
                    "cvssv3_impactScore": "3.6",
                    "cvssv3_version": "3.1",
                    "source": "NVD"
                },
                "defaultConfiguration": {
                    "level": "error"
                }
            }
        ],
        "properties": {
            "disclaimer": "Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user's risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.",
            "nvd": "This report contains data retrieved from the National Vulnerability Database: http://nvd.nist.gov",
            "npm": "This report may contain data retrieved from the NPM Public Advisories: https://www.npmjs.com/advisories",
            "retirejs": "This report may contain data retrieved from the RetireJS community: https://retirejs.github.io/retire.js/",
            "ossindex": "This report may contain data retrieved from the Sonatype OSS Index: https://ossindex.sonatype.org",
            "NVD CVE Checked": "2022-05-25T15:58:07",
            "NVD CVE Modified": "2022-05-25T14:00:01",
            "VersionCheckOn": "2022-05-25T15:58:07"
        }
    }
}

Tool information

  • Name: dependency-check
  • Organization: undefined
  • Version: undefined

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants