twine-6.1.0-py3-none-any.whl: 1 vulnerabilities (highest severity is: 4.8)

[mend-for-github-com]

Vulnerable Library - twine-6.1.0-py3-none-any.whl

Path to dependency file: /test_requirements.txt

Path to vulnerable library: /test_requirements.txt

Vulnerabilities

CVE	Severity	CVSS	Exploit Maturity	EPSS	Dependency	Type	Fixed in (twine version)	Remediation Possible**	Reachability
CVE-2024-12797	Medium	4.8	Not Defined	0.0%	cryptography-44.0.0-cp37-abi3-manylinux_2_28_x86_64.whl	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-12797

Vulnerable Library - cryptography-44.0.0-cp37-abi3-manylinux_2_28_x86_64.whl

cryptography is a package which provides cryptographic recipes and primitives to Python developers.

Library home page: https://files.pythonhosted.org/packages/b1/07/40fe09ce96b91fc9276a9ad272832ead0fddedcba87f1190372af8e3039c/cryptography-44.0.0-cp37-abi3-manylinux_2_28_x86_64.whl

Path to dependency file: /test_requirements.txt

Path to vulnerable library: /test_requirements.txt

Dependency Hierarchy:

• twine-6.1.0-py3-none-any.whl (Root Library)
  • keyring-25.5.0-py3-none-any.whl
    • SecretStorage-3.3.3-py3-none-any.whl
      • ❌ cryptography-44.0.0-cp37-abi3-manylinux_2_28_x86_64.whl (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

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

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