CVE-2018-10024
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 · uneditedubiQuoss Switch VP5208A creates a bcm_password file at /cgi-bin/ with the user credentials in cleartext when a failed login attempt occurs. The file can be reached via an HTTP request. The credentials can be used to access the system via SSH (or TELNET if it is enabled).
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 confidenceThe ubiQuoss VP5208A switch writes user credentials in cleartext to a file named 'bcm_password' in the /cgi-bin/ directory whenever a failed login attempt occurs. This file is accessible via HTTP, allowing unauthenticated remote attackers to retrieve valid credentials and gain administrative access via SSH or TELNET.
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 dataall versionsCVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Confirm device modelAccess the device web interface or check via SNMP/CLI and identify the exact model number. Look for 'VP5208A' or 'Ubiquoss' branding in the device interface or login page.Affected if The device is an Ubiquoss VP5208A switch
-
Verify HTTP service is enabledAttempt to access the device's web interface via HTTP on port 80. Check if the login page loads or if HTTP responses are received.Affected if HTTP is enabled and the device responds on port 80 (the vulnerability requires HTTP access to the file)
-
Access the bcm_password fileSend an HTTP GET request to http://[device-ip]/cgi-bin/bcm_password using a web browser or curl command. No authentication should be required.Affected if The file exists and is accessible without authentication, returning cleartext credentials or login attempt data
-
Check for Telnet service exposureAttempt to connect to the device via Telnet on port 23 using the retrieved credentials or test if port 23 is open.Affected if Telnet service is accessible and accepts the credentials found in the file
If the device is a Ubiquoss VP5208A with HTTP enabled and the /cgi-bin/bcm_password file is accessible, the device is affected by this vulnerability and credentials can be retrieved by unauthenticated attackers.
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 or disable HTTP access to /cgi-bin/, disable TELNET and enforce SSH with key-based authentication, and apply vendor firmware updates if available. If the device cannot be patched, consider network isolation or replacement.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10024 — 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-2018-10024 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