Availability loss via prematurely freed properties string
Published Apr 8, 2025 · Updated Jun 30, 2026
Use-after-free in rust-openssl 0.10.39 through 0.10.71 allows remote attackers to disrupt availability through affected fetch calls. Md::fetch and Cipher::fetch take a pointer from a temporary CString, then drop that string before OpenSSL reads the properties. A consuming application must call either function with Some(properties); the dangling pointer usually makes OpenSSL parse an empty property string.
Summary
What happened
Use-after-free in rust-openssl 0.10.39 through 0.10.71 allows remote attackers to disrupt availability through affected fetch calls. Md::fetch and Cipher::fetch take a pointer from a temporary CString, then drop that string before OpenSSL reads the properties. A consuming application must call either function with Some(properties); the dangling pointer usually makes OpenSSL parse an empty property string.
The record
- CVE
- CVE-2025-3416
- Published
- Apr 8, 2025
- Updated
- Jun 30, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 6
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo