reqwest-0.12.3.crate: 11 vulnerabilities (highest severity is: 9.1)

[mend-bolt-for-github]

Vulnerable Library - reqwest-0.12.3.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (reqwest version)	Remediation Possible**
CVE-2024-5535	Critical	9.1	openssl-src-300.2.3+3.2.1.crate	Transitive	N/A*	❌
CVE-2024-6119	High	7.5	openssl-src-300.2.3+3.2.1.crate	Transitive	N/A*	❌
CVE-2024-4741	High	7.5	openssl-src-300.2.3+3.2.1.crate	Transitive	N/A*	❌
CVE-2024-32650	High	7.5	rustls-0.22.3.crate	Transitive	N/A*	❌
CVE-2024-4603	Medium	5.3	openssl-src-300.2.3+3.2.1.crate	Transitive	N/A*	❌
CVE-2025-24898	Medium	4.8	openssl-0.10.64.crate	Transitive	N/A*	❌
CVE-2024-12797	Medium	4.8	openssl-src-300.2.3+3.2.1.crate	Transitive	N/A*	❌
CVE-2024-12224	Medium	4.8	idna-0.5.0.crate	Transitive	N/A*	❌
CVE-2024-9143	Medium	4.3	openssl-src-300.2.3+3.2.1.crate	Transitive	N/A*	❌
CVE-2024-2511	Low	3.7	openssl-src-300.2.3+3.2.1.crate	Transitive	N/A*	❌
CVE-2024-13176	Low	2.9	openssl-src-300.2.3+3.2.1.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-2024-5535

Vulnerable Library - openssl-src-300.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an
empty supported client protocols buffer may cause a crash or memory contents to
be sent to the peer.

Impact summary: A buffer overread can have a range of potential consequences
such as unexpected application beahviour or a crash. In particular this issue
could result in up to 255 bytes of arbitrary private data from memory being sent
to the peer leading to a loss of confidentiality. However, only applications
that directly call the SSL_select_next_proto function with a 0 length list of
supported client protocols are affected by this issue. This would normally never
be a valid scenario and is typically not under attacker control but may occur by
accident in the case of a configuration or programming error in the calling
application.

The OpenSSL API function SSL_select_next_proto is typically used by TLS
applications that support ALPN (Application Layer Protocol Negotiation) or NPN
(Next Protocol Negotiation). NPN is older, was never standardised and
is deprecated in favour of ALPN. We believe that ALPN is significantly more
widely deployed than NPN. The SSL_select_next_proto function accepts a list of
protocols from the server and a list of protocols from the client and returns
the first protocol that appears in the server list that also appears in the
client list. In the case of no overlap between the two lists it returns the
first item in the client list. In either case it will signal whether an overlap
between the two lists was found. In the case where SSL_select_next_proto is
called with a zero length client list it fails to notice this condition and
returns the memory immediately following the client list pointer (and reports
that there was no overlap in the lists).

This function is typically called from a server side application callback for
ALPN or a client side application callback for NPN. In the case of ALPN the list
of protocols supplied by the client is guaranteed by libssl to never be zero in
length. The list of server protocols comes from the application and should never
normally be expected to be of zero length. In this case if the
SSL_select_next_proto function has been called as expected (with the list
supplied by the client passed in the client/client_len parameters), then the
application will not be vulnerable to this issue. If the application has
accidentally been configured with a zero length server list, and has
accidentally passed that zero length server list in the client/client_len
parameters, and has additionally failed to correctly handle a "no overlap"
response (which would normally result in a handshake failure in ALPN) then it
will be vulnerable to this problem.

In the case of NPN, the protocol permits the client to opportunistically select
a protocol when there is no overlap. OpenSSL returns the first client protocol
in the no overlap case in support of this. The list of client protocols comes
from the application and should never normally be expected to be of zero length.
However if the SSL_select_next_proto function is accidentally called with a
client_len of 0 then an invalid memory pointer will be returned instead. If the
application uses this output as the opportunistic protocol then the loss of
confidentiality will occur.

This issue has been assessed as Low severity because applications are most
likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not
widely used. It also requires an application configuration or programming error.
Finally, this issue would not typically be under attacker control making active
exploitation unlikely.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Due to the low severity of this issue we are not issuing new releases of
OpenSSL at this time. The fix will be included in the next releases when they
become available.

Publish Date: 2024-06-27

URL: CVE-2024-5535

CVSS 3 Score Details (9.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2024-5535

Release Date: 2024-06-27

Fix Resolution: openssl-3.0.15,openssl-3.1.7,openssl-3.2.3,openssl-3.3.2

Step up your Open Source Security Game with Mend here

CVE-2024-6119

Vulnerable Library - openssl-src-300.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

Issue summary: Applications performing certificate name checks (e.g., TLS
clients checking server certificates) may attempt to read an invalid memory
address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of
service.

Applications performing certificate name checks (e.g., TLS clients checking
server certificates) may attempt to read an invalid memory address when
comparing the expected name with an otherName subject alternative name of an
X.509 certificate. This may result in an exception that terminates the
application program.

Note that basic certificate chain validation (signatures, dates, ...) is not
affected, the denial of service can occur only when the application also
specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they
generally don't perform a name check against a reference identifier (expected
identity), but rather extract the presented identity after checking the
certificate chain. So TLS servers are generally not affected and the severity
of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Publish Date: 2024-09-03

URL: CVE-2024-6119

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • 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/secadv/20240903.txt

Release Date: 2024-09-03

Fix Resolution: openssl-3.0.15,openssl-3.1.7,openssl-3.2.3,openssl-3.3.2, cryptography - 43.0.1

Step up your Open Source Security Game with Mend here

CVE-2024-4741

Vulnerable Library - openssl-src-300.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

A Use After Free exists in OpenSSL when calling the OpenSSL API function SSL_free_buffers, which may cause
memory to be accessed that was previously freed in some situations. only applications that directly call the SSL_free_buffers function are
affected by this issue. Fixed in commit e5093133c3 (for 3.3), commit c88c3de510 (for 3.2), commit 704f725b96 (for 3.1) and commit b3f0eb0a29
(for 3.0) in the OpenSSL git repository. It is available to premium support customers in commit f7a045f314 (for 1.1.1).

Publish Date: 2024-11-13

URL: CVE-2024-4741

CVSS 3 Score Details (7.5)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.openssl.org/news/secadv/20240528.txt

Release Date: 2024-05-10

Fix Resolution: openssl-3.0.14,openssl-3.1.6,openssl-3.2.2,openssl-3.3.1

Step up your Open Source Security Game with Mend here

CVE-2024-32650

Vulnerable Library - rustls-0.22.3.crate

Rustls is a modern TLS library written in Rust.

Library home page: https://static.crates.io/crates/rustls/rustls-0.22.3.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-rustls-0.25.0.crate
    • ❌ rustls-0.22.3.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

Rustls is a modern TLS library written in Rust. rustls::ConnectionCommon::complete_io could fall into an infinite loop based on network input. When using a blocking rustls server, if a client send a close_notify message immediately after client_hello, the server's complete_io will get in an infinite loop. This vulnerability is fixed in 0.23.5, 0.22.4, and 0.21.11.

Publish Date: 2024-04-19

URL: CVE-2024-32650

CVSS 3 Score Details (7.5)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-6g7w-8wpp-frhj

Release Date: 2024-04-19

Fix Resolution: rustls - 0.21.11,0.22.4,0.23.5

Step up your Open Source Security Game with Mend here

CVE-2024-4603

Vulnerable Library - openssl-src-300.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

Issue summary: Checking excessively long DSA keys or parameters may be very
slow.

Impact summary: Applications that use the functions EVP_PKEY_param_check()
or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may
experience long delays. Where the key or parameters that are being checked
have been obtained from an untrusted source this may lead to a Denial of
Service.

The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform
various checks on DSA parameters. Some of those computations take a long time
if the modulus (p parameter) is too large.

Trying to use a very large modulus is slow and OpenSSL will not allow using
public keys with a modulus which is over 10,000 bits in length for signature
verification. However the key and parameter check functions do not limit
the modulus size when performing the checks.

An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check()
and supplies a key or parameters obtained from an untrusted source could be
vulnerable to a Denial of Service attack.

These functions are not called by OpenSSL itself on untrusted DSA keys so
only applications that directly call these functions may be vulnerable.

Also vulnerable are the OpenSSL pkey and pkeyparam command line applications
when using the -check option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.

Publish Date: 2024-05-16

URL: CVE-2024-4603

CVSS 3 Score Details (5.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2024-4603

Release Date: 2024-05-16

Fix Resolution: openssl-3.0.14,openssl-3.1.6,openssl-3.2.2,openssl-3.3.1

Step up your Open Source Security Game with Mend here

CVE-2025-24898

Vulnerable Library - openssl-0.10.64.crate

OpenSSL bindings

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

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • ❌ openssl-0.10.64.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

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.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

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-12224

Vulnerable Library - idna-0.5.0.crate

IDNA (Internationalizing Domain Names in Applications) and Punycode.

Library home page: https://static.crates.io/crates/idna/idna-0.5.0.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • url-2.5.0.crate
    • ❌ idna-0.5.0.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

"idna" 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with "idna" 0.5.0 or earlier.
Concretely, "example.org" and "xn--example-.org" become equal after processing by "idna" 0.5.0 or earlier. Also, "example.org.xn--" and "example.org." become equal after processing by "idna" 0.5.0 or earlier.
In applications using "idna" (but not in "idna" itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an "xn--"-masked name that turns into the name of the target when processed by "idna" 0.5.0 or earlier.
Remedy
Upgrade to "idna" 1.0.3 or later, if depending on "idna" directly, or to "url" 2.5.4 or later, if depending on "idna" via "url". (This issue was fixed in "idna" 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)
When upgrading, please take a moment to read about "alternative Unicode back ends for "idna"" (https://docs.rs/crate/idna_adapter/latest).
If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an "issue" (servo/rust-url#992) about combining them with "url" 2.5.4 and "idna" 1.0.3.
Additional information
This issue resulted from "idna" 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in "revision 33 of UTS 46" (https://www.unicode.org/reports/tr46/tr46-33.html#Modifications).
Acknowledgements
Thanks to kageshiron for recognizing the security implications of this behavior.

Publish Date: 2025-02-02

URL: CVE-2024-12224

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: GHSA-h97m-ww89-6jmq

Release Date: 2024-12-09

Fix Resolution: idna - 1.0.0

Step up your Open Source Security Game with Mend here

CVE-2024-9143

Vulnerable Library - openssl-src-300.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted
explicit values for the field polynomial can lead to out-of-bounds memory reads
or writes.

Impact summary: Out of bound memory writes can lead to an application crash or
even a possibility of a remote code execution, however, in all the protocols
involving Elliptic Curve Cryptography that we're aware of, either only "named
curves" are supported, or, if explicit curve parameters are supported, they
specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent
problematic input values. Thus the likelihood of existence of a vulnerable
application is low.

In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,
so problematic inputs cannot occur in the context of processing X.509
certificates. Any problematic use-cases would have to be using an "exotic"
curve encoding.

The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),
and various supporting BN_GF2m_*() functions.

Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,
that make it possible to represent invalid field polynomials with a zero
constant term, via the above or similar APIs, may terminate abruptly as a
result of reading or writing outside of array bounds. Remote code execution
cannot easily be ruled out.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Publish Date: 2024-10-16

URL: CVE-2024-9143

CVSS 3 Score Details (4.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://seclists.org/oss-sec/2024/q4/33

Release Date: 2024-10-16

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

Step up your Open Source Security Game with Mend here

CVE-2024-2511

Vulnerable Library - openssl-src-300.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

Vulnerability Details

Issue summary: Some non-default TLS server configurations can cause unbounded
memory growth when processing TLSv1.3 sessions

Impact summary: An attacker may exploit certain server configurations to trigger
unbounded memory growth that would lead to a Denial of Service

This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is
being used (but not if early_data support is also configured and the default
anti-replay protection is in use). In this case, under certain conditions, the
session cache can get into an incorrect state and it will fail to flush properly
as it fills. The session cache will continue to grow in an unbounded manner. A
malicious client could deliberately create the scenario for this failure to
force a Denial of Service. It may also happen by accident in normal operation.

This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS
clients.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL
1.0.2 is also not affected by this issue.

Publish Date: 2024-04-08

URL: CVE-2024-2511

CVSS 3 Score Details (3.7)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://seclists.org/oss-sec/2024/q2/44

Release Date: 2024-04-08

Fix Resolution: openssl-3.0.14,openssl-3.1.6,openssl-3.2.2,OpenSSL_1_1_1y

Step up your Open Source Security Game with Mend here

CVE-2024-13176

Vulnerable Library - openssl-src-300.2.3+3.2.1.crate

Source of OpenSSL and logic to build it.

Library home page: https://static.crates.io/crates/openssl-src/openssl-src-300.2.3+3.2.1.crate

Path to dependency file: /Cargo.toml

Path to vulnerable library: /Cargo.toml

Dependency Hierarchy:

• reqwest-0.12.3.crate (Root Library)
  • tokio-native-tls-0.3.1.crate
    • native-tls-0.2.11.crate
      • openssl-0.10.64.crate
        • openssl-sys-0.9.102.crate
          • ❌ openssl-src-300.2.3+3.2.1.crate (Vulnerable Library)

Found in HEAD commit: 98188af4bd8974421a36fc56fa2d8f5f52e98124

Found in base branch: v6

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