CVE-2024-45721
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, Wi-Fi STATION SH-52B, and Wi-Fi STATION SH-54C contain an OS command injection vulnerability in the HOST name configuration screen. 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 HOST name configuration screen of home 5G HR02, Wi-Fi STATION SH-52B, and Wi-Fi STATION SH-54C allows an authenticated administrative user to execute arbitrary OS commands with root privileges via unsanitized input.
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 the device modelCheck the device label, admin interface, or web UI for the exact model number (HR02, SH-52B, or SH-54C)Affected if The device is a home 5G HR02, Wi-Fi STATION SH-52B, or Wi-Fi STATION SH-54C
-
Check firmware versionAccess the admin web interface, navigate to the system or status page, and record the firmware version displayedAffected if The firmware version falls within the affected range for the identified model (compare against vendor's vulnerability disclosure)
-
Verify admin interface accessibilityDetermine if the administrative web interface is reachable from the network (check for open ports 80/443 or the device's default admin port)Affected if The admin interface is exposed on the network without proper access controls
-
Confirm HOST name configuration accessLog into the admin interface and navigate to the HOST name configuration screen (typically under network settings, LAN settings, or device configuration)Affected if You can access the HOST name configuration screen and the parameter accepts user input without visible sanitization feedback
-
Inspect HTTP requests for the HOST name parameterUse browser developer tools or a proxy to capture the POST request when submitting the HOST name field; examine if the input is sent unsanitizedAffected if The HOST name value is transmitted as raw input without apparent encoding or validation in the request
You are affected if your device is one of the three listed models, your firmware version is vulnerable, and the administrative HOST name configuration screen is accessible with input acceptance capability.
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 dataImplement strict input validation and sanitization on the HOST name configuration parameter to prevent command injection. Avoid using user input in any system() or shell execution calls; if unavoidable, use parameterized approaches or allowlist validation.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45721 — 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-45721 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