CVE-2024-30973
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 · uneditedAn issue in V-SOL G/EPON ONU HG323AC-B with firmware version V2.0.08-210715 allows an attacker to execute arbtirary code and obtain sensitive information via crafted POST request to /boaform/getASPdata/formFirewall, /boaform/getASPdata/formAcc.
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 · moderate confidenceThe V-SOL HG323AC-B router firmware V2.0.08-210715 contains a command injection vulnerability in its web interface. Specifically, crafted POST requests to the /boaform/getASPdata/formFirewall and /boaform/getASPdata/formAcc endpoints allow unauthenticated attackers to execute arbitrary code on the device and extract sensitive information.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 modelAccess the router web interface and check the system status or device info page, or inspect the device label for model HG323AC-BAffected if Device model is V-SOL HG323AC-B
-
Check the firmware versionLog into the router web interface and navigate to the firmware/version information page, or use a firmware extraction tool if you have a firmware fileAffected if Firmware version is V2.0.08-210715 or earlier
-
Verify web management interface accessibilityAttempt to access the router web interface (HTTP/HTTPS on common ports like 80, 443, 8080) from an untrusted network perspectiveAffected if The web management interface is exposed to untrusted or public networks without network segmentation
-
Confirm the vulnerable endpoints respondSend a GET request to /boaform/getASPdata/formFirewall and /boaform/getASPdata/formAcc and verify they return a valid HTTP responseAffected if These endpoints are accessible and return HTTP 200 responses, indicating the vulnerable web application is running
You are affected if you have a V-SOL HG323AC-B router running firmware V2.0.08-210715 (or earlier) with its web interface accessible to untrusted networks, as the command injection requires no authentication.
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 dataUpdate to a patched firmware version if available from V-SOL; otherwise, isolate the device behind a firewall or restrict access to the web management interface to trusted networks only.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30973 — 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-30973 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