CVE-2025-0306
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2025-0306 is a high-severity Covert Timing Channel (CWE-385) vulnerability. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-31 (Covert Channel Analysis) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-0306 is a vulnerability in the Ruby interpreter that exposes it to the Marvin Attack. Published on 2025-01-09, this issue is classified under CWE-385 and carries a CVSS v3.1 base score of 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), indicating high confidentiality and integrity impacts with no availability effects.
The attack requires a remote, unauthenticated adversary to engage the vulnerable service over the network, though it demands high complexity with no user interaction needed. By exchanging a large number of messages with the service, the attacker can decrypt previously encrypted messages or forge signatures.
Mitigation guidance is provided in vendor advisories, including Red Hat security updates at https://access.redhat.com/security/cve/CVE-2025-0306 and https://bugzilla.redhat.com/show_bug.cgi?id=2336100, as well as NetApp advisory ntap-20250221-0009/ at https://security.netapp.com/advisory/ntap-20250221-0009/.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-1595
Vulnerability Data
A vulnerability was found in Ruby. The Ruby interpreter is vulnerable to the Marvin Attack. This attack allows the attacker to decrypt previously encrypted messages or forge signatures by exchanging a large number of messages with the vulnerable service.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Covert channel analysis directly identifies timing channels that could leak information.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices (reviews, testing) directly reduce introduction of timing-channel vulnerabilities in code.
Runtime monitoring of hardware/software behavior can detect anomalous timing patterns that indicate covert channels.
Vulnerability identification processes can surface timing-channel weaknesses during design or code analysis.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Detailed logging can reveal timing anomalies but does not prevent covert timing channels.
Continuous monitoring may detect timing-based exfiltration but does not eliminate the channel itself.
Network segmentation reduces attack surface but does not address intra-process timing channels.
Network segregation limits external timing observation but not internal covert timing.
Secure architecture principles can include timing-channel countermeasures but are not specific.
Secure coding guidelines may recommend constant-time algorithms but coverage is not guaranteed.