Repository navigation
chore(vex): record not_affected for log4j-core 2.14.1 fixture strings - #345
Merged
Merged
Conversation
log4j-core is not a dependency of this Go module. The 2.14.1 matches for CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 and CVE-2021-44832 come from example strings in test fixtures, golden files, help text and docs, which are kept as they are. Commit OpenVEX statements under .vulnetix/vex and add a VexSource in .vulnetix/config so every Vulnetix scan applies them before its gates.
Contributor
Vulnetix config planManager
0 to create, 1 to update, 0 to delete, 0 unchanged |
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
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.
Records
not_affectedOpenVEX statements for the log4j-core 2.14.1 matches (CVE-2021-44228, finding771e2df5-dc09-44f8-999d-eb68ffb73647, and the related CVE-2021-45046, CVE-2021-45105, CVE-2021-44832). The fixtures stay as they are.Same layout as Vulnetix/website: one OpenVEX document per finding under
.vulnetix/vex/, read by every Vulnetix scan through aVexSourcein.vulnetix/config/.What changes
.vulnetix/vex/CVE-2021-{44228,45046,45105,44832}.openvex.json: OpenVEX v0.2.0. Productpkg:github/Vulnetix/cli, subcomponentpkg:maven/org.apache.logging.log4j/log4j-core@2.14.1, statusnot_affected, justificationcomponent_not_present..vulnetix/config/vex.yaml:VexSourcewithspec.path: .vulnetix/vex, scoped toVulnetix/cli. Scans readpathVexSources without a flag (docs/vex-sources.md), and an authenticated scan sends the documents tocli.vex-ingest, which turns thenot_affectedstatements into organisation suppression rules on the platform..gitignore:.vulnetix/becomes.vulnetix/*with!.vulnetix/vex/and!.vulnetix/config/; the duplicatedworkflow.yamlnegation is dropped.Why not affected
This is a Go module (go.mod / go.sum only). There is no Maven or Gradle build and no JAR in the shipped CLI. log4j-core 2.14.1 appears only as literal strings:
internal/reportfixtures and goldens,cmd/help text and tests,internal/agenttests, docs, and the SAST rule-efficacy data underinternal/sast/testdata.Verification
vulnetix vex validate --vex .vulnetix/vex/: 4 statements, no problems.vulnetix vex apply --vex .vulnetix/vex/ --bom <CycloneDX with log4j-core@2.14.1 + CVE-2021-44228>:VEX not affected 1, matched onsubcomponent, effective 0.Closes #304
Closes #216
Closes #215