Description
CVE-2024-0727 found in deb/debian/[email protected]~deb12u2
Important
Risk: 1.70 (Low)
CVSS: 5.5
Description
Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL
to crash leading to a potential Denial of Service attack
Impact summary: Applications loading files in the PKCS12 format from untrusted
sources might terminate abruptly.
A file in PKCS12 format can contain certificates and keys and may come from an
untrusted source. The PKCS12 specification allows certain fields to be NULL, but
OpenSSL does not correctly check for this case. This can lead to a NULL pointer
dereference that results in OpenSSL crashing. If an application processes PKCS12
files from an untrusted source using the OpenSSL APIs then that application will
be vulnerable to this issue.
OpenSSL APIs that are vulnerable to this are: PKCS12_parse(),
PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes()
and PKCS12_newpass().
We have also fixed a similar issue in SMIME_write_PKCS7(). However since this
function is related to writing data we do not consider it security significant.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
Affected component
The vulnerability is in pkg:deb/debian/[email protected]~deb12u2, detected by github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning, github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning:test.
Recommended fix
No fix is available.
Additional guidance for mitigating vulnerabilities
Visit our guides on devguard.org
See more details...
Path to component
%%{init: { 'theme':'base', 'themeVariables': {
'primaryColor': '#F3F3F3',
'primaryTextColor': '#0D1117',
'primaryBorderColor': '#999999',
'lineColor': '#999999',
'secondaryColor': '#ffffff',
'tertiaryColor': '#ffffff'
} }}%%
flowchart TD
root(["root"]) --- github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning"])
github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning"]) --- debian_12_7(["debian\@12.7"])
debian_12_7(["debian\@12.7"]) --- debian_ca_certificates(["debian/ca-certificates"])
debian_ca_certificates(["debian/ca-certificates"]) --- debian_openssl(["debian/openssl"])
root(["root"]) --- github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning_test(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning:test"])
github_com_l3montree_dev_devguard_cmd_devguard_scanner_container_scanning_test(["github.com/l3montree-dev/devguard/cmd/devguard-scanner/container-scanning:test"]) --- debian_12_7(["debian\@12.7"])
classDef default stroke-width:2px
| Risk Factor | Value | Description |
|---|---|---|
| Vulnerability Depth | 1 |
The vulnerability is in a direct dependency of your project. |
| EPSS | 0.23 % |
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days. |
| EXPLOIT | Not available |
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database. There are no script kiddies exploiting this vulnerability. |
| CVSS-BE | 3.7 |
- Exploiting this vulnerability significantly impacts availability. |
| CVSS-B | 5.5 |
- The vulnerability requires local access to the device to be exploited. - It is easy for an attacker to exploit this vulnerability. - An attacker does not need any special privileges or access rights. - The attacker needs the user to perform some action, like clicking a link. - The impact is confined to the system where the vulnerability exists. - There is a high impact on the availability of the system. |
More details can be found in DevGuard
Interact with this vulnerability
You can use the following slash commands to interact with this vulnerability:
👍 Reply with this to acknowledge and accept the identified risk.
/accept I accept the risk of this vulnerability, because ...
⚠️ Mark the risk as false positive: Use one of these commands if you believe the reported vulnerability is not actually a valid issue.
/component-not-present The vulnerable component is not included in the artifact.
/vulnerable-code-not-present The component is present, but the vulnerable code is not included or compiled.
/vulnerable-code-not-in-execute-path The vulnerable code exists, but is never executed at runtime.
/vulnerable-code-cannot-be-controlled-by-adversary Built-in protections prevent exploitation of this vulnerability.
/inline-mitigations-already-exist The vulnerable code cannot be controlled or influenced by an attacker.
🔁 Reopen the risk: Use this command to reopen a previously closed or accepted vulnerability.
/reopen ...