CVE-2024-54082
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedhome 5G HR02 and Wi-Fi STATION SH-54C contain an OS command injection vulnerability in the configuration restore function. An arbitrary OS command may be executed with the root privilege by an administrative user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in the configuration restore function of home 5G HR02 and Wi-Fi STATION SH-54C routers/mobile hotspots. An authenticated administrative user can execute arbitrary OS commands with root privileges due to insufficient input sanitization in the config restore feature.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelLocate the device label or access the admin web interface (typically at 192.168.0.1 or 192.168.1.1) to confirm the model number is either home 5G HR02 or Wi-Fi STATION SH-54CAffected if Device is either HR02 or SH-54C model
-
Check firmware versionIn the router admin interface, navigate to Settings or System Information to view the installed firmware version. Compare against any available vendor firmware release notesAffected if Firmware version is unpatched (no official patch version specified)
-
Verify config restore feature accessibilityAccess the router admin panel and locate the Configuration Backup/Restore or Settings Import function. Determine if this feature is exposed to the network or only accessible via local admin interfaceAffected if Config restore feature is accessible remotely or via web interface without additional network restrictions
-
Confirm remote administrative access statusIn router settings, check if Remote Management, Remote Administration, or TR-069 settings are enabled. Look for options allowing admin access from WAN/internetAffected if Remote admin access is enabled, allowing potential authenticated attackers to reach the vulnerability
-
Inspect for indicators of compromiseReview router system logs or traffic logs for unexpected configuration restore events, unusual scheduled tasks, or commands executed around the time of suspected exploitationAffected if Unexpected config restore events appear in logs or unknown processes are running with elevated privileges
A user is affected if they operate an HR02 or SH-54C device with the config restore feature accessible to unauthenticated or weakly-protected administrative interfaces, especially if remote admin access is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict administrative interface access to trusted IP addresses only, apply vendor firmware updates when available, and implement network segmentation to limit exposure. If no patch exists, consider compensating controls such as disabling remote admin access and monitoring for indicators of compromise.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54082 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data