[GHSA-94jh-j374-9r3j] Refining Attack Requirement to Reflect Dependency on Physical Host for Successful Exploitation #5157
+2
−2
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.
I am collaborating with @vulnerability-analyst to enhance the accuracy of the OSS vulnerability advisories.
In alignment with the feedback from @shelbyc in this PR, the Attack Requirement (
AT
) should be updated toP
(Present) rather than the erroneousN
(None). This is because if the attacker submits a job to the container, he/she will not gain the root privileges.The sentence underlined above represents the “specific deployment and execution conditions” required for a successful attack, as defined in the CVSS 4 specification:
Overall, this vulnerability describes the following scenario:
libcrypto.so
library and place it in a writable directory within the modified search path$ORIGIN/:../lib/native/
. When thecontainer-executor
binary (which requires root privileges) is invoked, it may load the attacker’s malicious library instead of the legitimatelibcrypto.so
.