Credential disclosure via hardcoded XOR key
Published Feb 10, 2021 · Updated Aug 3, 2024
Hard-coded cryptographic key use in FiberHome HG6245D RP2613 and earlier allows attackers to recover credentials via firmware analysis. The webs binary uses a fixed XOR key in decrypt_password() to reversibly transform credential values stored in /fhconf/umconfig.txt. Access to the firmware or configuration file is required, after which the recovered credentials expose the accounts and services they protect.
Summary
What happened
Hard-coded cryptographic key use in FiberHome HG6245D RP2613 and earlier allows attackers to recover credentials via firmware analysis. The webs binary uses a fixed XOR key in decrypt_password() to reversibly transform credential values stored in /fhconf/umconfig.txt. Access to the firmware or configuration file is required, after which the recovered credentials expose the accounts and services they protect.
The record
- CVE
- CVE-2021-27141
- Published
- Feb 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- HG6245D XOR credential-decryption procedureproof of concept · demonstrated
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