dbcve.org
Aterm Wg1800hp4 FirmwareOperating system · Nec

CVE-2024-28006

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Improper authentication vulnerability in NEC Corporation Aterm WG1800HP4, WG1200HS3, WG1900HP2, WG1200HP3, WG1800HP3, WG1200HS2, WG1900HP, WG1200HP2, W1200EX(-MS), WG1200HS, WG1200HP, WF300HP2, W300P, WF800HP, WR8165N, WG2200HP, WF1200HP2, WG1800HP2, WF1200HP, WG600HP, WG300HP, WF300HP, WG1800HP, WG1400HP, WR8175N, WR9300N, WR8750N, WR8160N, WR9500N, WR8600N, WR8370N, WR8170N, WR8700N, WR8300N, WR8150N, WR4100N, WR4500N, WR8100N, WR8500N, CR2500P, WR8400N, WR8200N, WR1200H, WR7870S, WR6670S, WR7850S, WR6650S, WR6600H, WR7800H, WM3400RN, WM3450RN, WM3500R, WM3600R, WM3800R, WR8166N, MR01LN MR02LN, WG1810HP(JE) and WG1810HP(MF) all versions allows a attacker to view device information.

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 confidence

This is an improper authentication vulnerability in multiple NEC Aterm wireless router models. The vulnerability allows an unauthenticated attacker to view device information, indicating a broken access control where certain pages or API endpoints that should require authentication can be accessed without valid credentials. The specific attack vector (e.g., direct URL manipulation, missing session checks, hardcoded credentials) is not specified in the available description.

MitigationApply any vendor-supplied firmware updates when available. If no update exists, implement network segmentation to isolate affected devices from untrusted networks and restrict management interface access to authorized IP ranges only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aterm Wg1800hp4 FirmwareOperating system
Affected:all versions
Aterm Wg1200hs3 FirmwareOperating system
Affected:all versions
Aterm Wg1900hp2 FirmwareOperating system
Affected:all versions
Aterm Wg1200hp3 FirmwareOperating system
Affected:all versions
Aterm Wg1800hp3 FirmwareOperating system
Affected:all versions
Aterm Wr7850s FirmwareOperating system
Affected:all versions
Aterm Wr6650s FirmwareOperating system
Affected:all versions
Aterm Wr6600h FirmwareOperating system
Affected:all versions

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Aterm router model
    Locate the model number on the device label or check the web interface login page for the model identifier
    Affected if The model matches any of these: Wg1800hp4, Wg1200hs3, Wg1900hp2, Wg1200hp3, Wg1800hp3, Wr7850s, Wr6650s, Wr6600h
  2. Confirm firmware version is present
    Access the router web management interface and navigate to the status or system information page to view the firmware version
    Affected if The router is running any firmware version on an affected model (all versions are vulnerable)
  3. Verify management interface is network-accessible
    From a host on the same network as the router, attempt to reach the router web interface IP address on HTTP/HTTPS ports (typically 80/443)
    Affected if The management web interface is reachable over the network
  4. Test unauthenticated access to device information
    Without logging in, attempt to access common status or info endpoints on the router web interface (such as status pages, device info, or network configuration pages)
    Affected if Device information, status pages, or configuration data is displayed without prompting for login credentials

You are affected if you own any of the listed Aterm models and can access device information or status pages through the web interface without being required to authenticate.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any vendor-supplied firmware updates when available. If no update exists, implement network segmentation to isolate affected devices from untrusted networks and restrict management interface access to authorized IP ranges only.

Fix this in Aterm Wg1800hp4 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28006 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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