Wi Fi Station L 02f FirmwareOperating system · Nttdocomo

CVE-2017-10846

HIGH · 7.5 CVSS v3.0 Published 2017-09-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Wi-Fi STATION L-02F Software version V10b and earlier allows remote attackers to bypass access restrictions to obtain information on device settings via unspecified vectors.

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

The L-02F Wi-Fi station device with firmware V10b and earlier contains an access control bypass vulnerability allowing remote unauthenticated attackers to retrieve sensitive device configuration information. The attack vector is network-based and requires no authentication, as the access restrictions protecting settings pages can be circumvented.

MitigationApply the vendor firmware update (version later than V10b) to address the access control bypass. If no update is available, consider network segmentation to limit exposure and monitor for unauthorized access attempts to device management interfaces.

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
Wi Fi Station L 02f FirmwareOperating system
Affected:<= v10b

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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the device model
    Locate the Wi-Fi station device on your network and confirm it is the L-02F model from Nttdocomo. Check the device label, management interface, or network inventory for the exact model designation.
    Affected if The device is not an L-02F model - different models are not affected by this specific CVE.
  2. Check the installed firmware version
    Access the device management web interface or use the vendor-provided diagnostic tool to retrieve the current firmware version. Compare the version string to the affected range V10b and earlier.
    Affected if The firmware version is V10b or any version earlier than V10b - these versions contain the access control bypass vulnerability.
  3. Verify network exposure of management interface
    Determine if the device management interface (HTTP/HTTPS ports for administrative access) is accessible from untrusted network segments or the public internet. Check firewall rules, NAT configurations, and interface binding settings.
    Affected if The management interface is exposed to untrusted networks - the vulnerability is network-exploitable and allows remote unauthenticated access.
  4. Test for unauthorized settings page access
    Attempt to access device configuration pages directly via HTTP requests without providing authentication credentials. Observe whether sensitive configuration data is returned without requiring login.
    Affected if Settings pages return sensitive configuration information without authentication - the access control bypass is present.

The device is affected if it is an L-02F model running firmware V10b or earlier with its management interface network-accessible, and unauthenticated access to settings pages is possible.

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 the vendor firmware update (version later than V10b) to address the access control bypass. If no update is available, consider network segmentation to limit exposure and monitor for unauthorized access attempts to device management interfaces.

Fix this in Wi Fi Station L 02f Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10846 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-10846 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