Secret-key exposure via premature KeyLocker destruction
Published Apr 24, 2023 · Updated Feb 4, 2025
Sensitive key exposure in Ribose RNP 0.16.1 through 0.16.2 allows attackers to access secret keys left unlocked after use. Premature destruction of an unnamed KeyLocker prevents it from re-locking some temporarily unlocked keys, leaving sensitive key material accessible in memory. Exploitation requires access to the affected application's memory after a key operation; the flaw does not itself alter keys or execute code.
Summary
What happened
Sensitive key exposure in Ribose RNP 0.16.1 through 0.16.2 allows attackers to access secret keys left unlocked after use. Premature destruction of an unnamed KeyLocker prevents it from re-locking some temporarily unlocked keys, leaving sensitive key material accessible in memory. Exploitation requires access to the affected application's memory after a key operation; the flaw does not itself alter keys or execute code.
The record
- CVE
- CVE-2023-29480
- Published
- Apr 24, 2023
- Updated
- Feb 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-922, CWE-312, CAPEC-37, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 4, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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