CVE-2025-3416: Rust-openssl: rust-openssl use-after-free in `md::fetch` and `cipher::fetch`
A flaw was found in OpenSSL's handling of the properties argument in certain functions. This vulnerability can allow use-after-free exploitation, which may result in undefined behavior or incorrect property parsing, leading to OpenSSL treating the input as an empty string.
Security readout for executives and security teams
Plain-English summary
This is a low-severity memory-safety issue in rust-openssl. Under specific conditions, OpenSSL property text may be read after being freed, causing undefined behavior or incorrect parsing. The published impact is limited to low availability impact, with no stated confidentiality or integrity impact.
Executive priority
Treat this as routine patch management unless affected components protect critical or internet-facing services. The published severity is low, exploitation evidence is absent, and business urgency should focus on accurate inventory and normal vendor update cycles.
Technical view
CVE-2025-3416 is a CWE-416 use-after-free affecting rust-openssl `md::fetch` and `cipher::fetch`, reported for version 0.10.39. The properties argument can be mishandled, leading to undefined behavior or being parsed as an empty string. CVSS is 3.7, network vector, high attack complexity.
Likely exposure
Exposure is most likely where applications or packaged components use the affected rust-openssl version or Red Hat-listed affected packages, including Directory Server and selected RHEL packages. The source bundle lists affected products but does not prove every deployment is reachable or exploitable.
Exploitation context
No active exploitation is supported by the provided sources, and the CVE is not listed as KEV. The CVSS vector indicates remote reachability but high attack complexity and only low availability impact. Evidence for practical exploitation is incomplete.
Researcher notes
The key uncertainty is practical reachability: sources describe the memory-safety flaw and affected package families, but not real-world exploitability. Researchers should verify dependency versions, vendor backports, and whether property arguments are attacker-influenced in deployed applications.
Mitigation direction
Check RustSec, upstream GitHub, and Red Hat guidance for fixed releases or backported packages.
Upgrade or rebuild applications using affected rust-openssl versions when a fixed release is available.
Apply Red Hat package updates for affected RHEL and Directory Server components when published.
Prioritize internet-facing or security-sensitive services that depend on affected cryptographic fetch paths.
Validation and detection
Inventory Rust dependency lockfiles for rust-openssl 0.10.39 or vulnerable transitive dependencies.
Compare Red Hat systems against the affected package list in Red Hat’s CVE entry.
Confirm installed package builds include the upstream fix or a vendor backport.
Review application use of `md::fetch` and `cipher::fetch` without creating exploit tests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.