Legacy TLS exposure via firmware configuration reset
Published Aug 6, 2024 · Updated Mar 24, 2025
Insecure default initialization in Ricoh JavaTM Platform 12.89 and earlier subjects device communications to legacy-TLS weaknesses. Updating firmware from an affected version resets the platform configuration by enabling TLS 1.0 and TLS 1.1 even when those protocols were disabled. JPCERT's evaluated scenario requires high privileges and adjacent access to run the Ricoh firmware-update tool; the bounded consequence is re-enablement of deprecated TLS protocols.
Summary
What happened
Insecure default initialization in Ricoh JavaTM Platform 12.89 and earlier subjects device communications to legacy-TLS weaknesses. Updating firmware from an affected version resets the platform configuration by enabling TLS 1.0 and TLS 1.1 even when those protocols were disabled. JPCERT's evaluated scenario requires high privileges and adjacent access to run the Ricoh firmware-update tool; the bounded consequence is re-enablement of deprecated TLS protocols.
The record
- CVE
- CVE-2024-41995
- Published
- Aug 6, 2024
- Updated
- Mar 24, 2025
- Vendor
- Oracle
- Product
- Java Platform, Standard Edition (Java SE)
- Classifications
- CWE-1188
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Aug 6, 2024CVE publishedPublication date reported by the CVE source.
- Mar 24, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <12.89
- Affected versionversion=Ver.12.89 and earlier
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