CVE-2024-4741
No exploitation reported by the sources we read.
- Published2024-11-13
- Fixed in3.3.1 · 3.2.2 · 3.1.6 · 3.0.14 · 1.1.1y
- WeaknessCWE-416
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Timeline
dates in UTC- 2024-11-1311:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-4741?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-4741?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.3 | ≥ 3.3.0, < 3.3.1 | 3.3.1 | CISA-ADP |
| 3.2 | ≥ 3.2.0, < 3.2.2 | 3.2.2 | CISA-ADP |
| 3.1 | ≥ 3.1.0, < 3.1.6 | 3.1.6 | CISA-ADP |
| 3.0 | ≥ 3.0.0, < 3.0.14 | 3.0.14 | CISA-ADP |
| 1.1 | ≥ 1.1.1, < 1.1.1y | 1.1.1y | CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- opensslAlmaLinux:9all versions · fixed in 1:3.2.2-6.el9_5and 3 other packages
- opensslAlmaLinux:8all versions · fixed in 1:1.1.1k-16.el8_6and 3 other packages
Fix
- Update OpenSSL to 3.3.1 · 3.2.2 · 3.1.6 · 3.0.14 · 1.1.1y
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2024-11-13
- Last Modified
- 2026-06-17
- NVD status
- Deferred
Frequently asked questions
What is CVE-2024-4741?
Is CVE-2024-4741 actively exploited?
What is the CVSS score for CVE-2024-4741?
Running OpenSSL? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.