openssl-0.10.68.crate: 3 vulnerabilities (highest severity is: 4.8)

[mend-bolt-for-github]

Vulnerable Library - openssl-0.10.68.crate

OpenSSL bindings

Library home page: https://static.crates.io/crates/openssl/openssl-0.10.68.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (openssl version)	Remediation Possible**
CVE-2025-24898	Medium	4.8	openssl-0.10.68.crate	Direct	openssl - 0.10.70	❌
CVE-2024-12797	Medium	4.8	openssl-src-300.4.0+3.4.0.crate	Transitive	N/A*	❌
CVE-2024-13176	Low	2.9	openssl-src-300.4.0+3.4.0.crate	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2025-24898

Vulnerable Library - openssl-0.10.68.crate

OpenSSL bindings

Library home page: https://static.crates.io/crates/openssl/openssl-0.10.68.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• ❌ openssl-0.10.68.crate (Vulnerable Library)

Found in base branch: main

Vulnerability Details

rust-openssl is a set of OpenSSL bindings for the Rust programming language. In affected versions "ssl::select_next_proto" can return a slice pointing into the "server" argument's buffer but with a lifetime bound to the "client" argument. In situations where the "sever" buffer's lifetime is shorter than the "client" buffer's, this can cause a use after free. This could cause the server to crash or to return arbitrary memory contents to the client. The crate"openssl" version 0.10.70 fixes the signature of "ssl::select_next_proto" to properly constrain the output buffer's lifetime to that of both input buffers. Users are advised to upgrade. In standard usage of "ssl::select_next_proto" in the callback passed to "SslContextBuilder::set_alpn_select_callback", code is only affected if the "server" buffer is constructed within the callback.

Publish Date: 2025-02-03

URL: CVE-2025-24898

CVSS 3 Score Details (4.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2025-02-03

Fix Resolution: openssl - 0.10.70

Step up your Open Source Security Game with Mend here

CVE-2024-12797

Vulnerable Library - openssl-src-300.4.0+3.4.0.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.4.0+3.4.0.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• openssl-0.10.68.crate (Root Library)
  • openssl-sys-0.9.104.crate
    • ❌ openssl-src-300.4.0+3.4.0.crate (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a
server may fail to notice that the server was not authenticated, because
handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode
is set.
Impact summary: TLS and DTLS connections using raw public keys may be
vulnerable to man-in-middle attacks when server authentication failure is not
detected by clients.
RPKs are disabled by default in both TLS clients and TLS servers. The issue
only arises when TLS clients explicitly enable RPK use by the server, and the
server, likewise, enables sending of an RPK instead of an X.509 certificate
chain. The affected clients are those that then rely on the handshake to
fail when the server's RPK fails to match one of the expected public keys,
by setting the verification mode to SSL_VERIFY_PEER.
Clients that enable server-side raw public keys can still find out that raw
public key verification failed by calling SSL_get_verify_result(), and those
that do, and take appropriate action, are not affected. This issue was
introduced in the initial implementation of RPK support in OpenSSL 3.2.
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Publish Date: 2025-02-11

URL: CVE-2024-12797

CVSS 3 Score Details (4.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://openssl-library.org/news/secadv/20250211.txt

Release Date: 2025-02-11

Fix Resolution: openssl-3.2.4,openssl-3.3.2,openssl-3.4.1, cryptography - 44.0.1

Step up your Open Source Security Game with Mend here

CVE-2024-13176

Vulnerable Library - openssl-src-300.4.0+3.4.0.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.4.0+3.4.0.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• openssl-0.10.68.crate (Root Library)
  • openssl-sys-0.9.104.crate
    • ❌ openssl-src-300.4.0+3.4.0.crate (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Issue summary: A timing side-channel which could potentially allow recovering
the private key exists in the ECDSA signature computation.
Impact summary: A timing side-channel in ECDSA signature computations
could allow recovering the private key by an attacker. However, measuring
the timing would require either local access to the signing application or
a very fast network connection with low latency.
There is a timing signal of around 300 nanoseconds when the top word of
the inverted ECDSA nonce value is zero. This can happen with significant
probability only for some of the supported elliptic curves. In particular
the NIST P-521 curve is affected. To be able to measure this leak, the attacker
process must either be located in the same physical computer or must
have a very fast network connection with low latency. For that reason
the severity of this vulnerability is Low.

Publish Date: 2025-01-20

URL: CVE-2024-13176

CVSS 3 Score Details (2.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://openssl-library.org/news/vulnerabilities/index.html#CVE-2024-13176

Release Date: 2025-01-20

Fix Resolution: openssl-3.0.16,openssl-3.1.8,openssl-3.2.4,openssl-3.3.3,openssl-3.4.1

Step up your Open Source Security Game with Mend here