RSA private-key disclosure via embedded credentials
Published Feb 13, 2020 · Updated Aug 6, 2024
Hard-coded credentials in QNAP VioCard 300 firmware builds RS_B3722 and RS_B4631 allow remote attackers to read RSA private keys. The firmware image stores reusable private-key material as fixed data instead of protecting a device-specific secret. No authentication or user interaction is required, and the published impact is limited to disclosure; the keys' operational role is undisclosed.
Summary
What happened
Hard-coded credentials in QNAP VioCard 300 firmware builds RS_B3722 and RS_B4631 allow remote attackers to read RSA private keys. The firmware image stores reusable private-key material as fixed data instead of protecting a device-specific secret. No authentication or user interaction is required, and the published impact is limited to disclosure; the keys' operational role is undisclosed.
The record
- CVE
- CVE-2013-6277
- Published
- Feb 13, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record 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
- firmware.re USENIX Security 2014 exploit materialsproof of concept · unverified
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