CVE-2018-15358
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 authenticated attacker with low privileges can activate high privileged user and use it to expand attack surface in Eltex ESP-200 firmware version 1.2.0.
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 Eltex ESP-200 firmware 1.2.0 contains an insecure privilege escalation vulnerability where an authenticated attacker with low-privilege credentials can activate a high-privileged user account. This allows the attacker to bypass authorization controls and gain administrative access to expand the attack surface.
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= 1.2.0CVSS 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.0/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 device model and firmware versionAccess the Eltex ESP-200 web interface or CLI and navigate to the system status or firmware information page. Alternatively, check via SNMP using the OID for device information or review the boot logs.Affected if The device model is Eltex ESP-200 and the firmware version is exactly 1.2.0
-
Verify user account configuration existsLog into the device management interface and navigate to the user accounts or administration section. Check if multiple user accounts are configured with different privilege levels.Affected if Multiple user accounts exist with varying privilege levels (e.g., administrator and regular user)
-
Confirm account management functionality is accessible to low-privilege usersLog in using a low-privilege (non-administrator) account and attempt to access the user account management or user activation features within the web interface.Affected if A low-privilege authenticated user can access the account management or user activation interface
-
Check for active high-privilege accountsWith the low-privilege account, examine whether there are options to activate, enable, or modify high-privilege administrator accounts.Affected if Low-privilege users can view or modify the status of administrator or high-privilege accounts
You are affected if the device is an Eltex ESP-200 running firmware version 1.2.0 and low-privilege authenticated users can access account activation or management features for higher-privilege accounts.
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 dataUpgrade to a patched firmware version that implements proper server-side authorization checks to ensure low-privilege users cannot modify or activate high-privilege accounts. If no patch is available, restrict network access to the device management interface to trusted users only.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15358 — 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-15358 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