Menu

Star on GitHub · 3.2k

CVE-2024-3219

The “socket” module provides a pure-Python fallback to the socket.socketpair() function for platforms that don’t support AF_UNIX, such as Windows.

Published Jul 29, 2024CWE-306EPSS 0.25%

Overview

CVE-2024-3219 is a known-severity vulnerability. It was published on July 29, 2024.

Technical description

The

“socket” module provides a pure-Python fallback to the

socket.socketpair() function for platforms that don’t support AF_UNIX,

such as Windows. This pure-Python implementation uses AF_INET or

AF_INET6 to create a local connected pair of sockets. The connection

between the two sockets was not verified before passing the two sockets

back to the user, which leaves the server socket vulnerable to a

connection race from a malicious local peer.

Platforms that support AF_UNIX such as Linux and macOS are not affected by this vulnerability. Versions prior to CPython 3.5 are not affected due to the vulnerable API not being included.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2024-3219?

CVE-2024-3219 is a known-severity vulnerability. It was published on July 29, 2024.

How severe is CVE-2024-3219?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2024-3219?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-3219?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-3219 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.