CVE-2018-14805
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 · uneditedABB eSOMS version 6.0.2 may allow unauthorized access to the system when LDAP is set to allow anonymous authentication, and specific key values within the eSOMS web.config file are present. Both conditions are required to exploit this vulnerability.
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 confidenceABB eSOMS version 6.0.2 contains an authentication bypass vulnerability where unauthorized access to the system is possible when LDAP is configured to allow anonymous authentication in combination with specific sensitive key values present in the eSOMS web.config file. Both conditions must be present for exploitation.
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= 6.0.2CVSS 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.
-
Verify eSOMS version is 6.0.2Check the installed eSOMS version through the application UI or system information files. Compare against the affected version 6.0.2.Affected if The installed version is exactly 6.0.2 (this specific version is affected)
-
Locate and inspect the eSOMS web.config fileFind the web.config file in the eSOMS installation directory (typically in the web application root folder). Open and examine its contents for the presence of sensitive key values.Affected if Sensitive key values are present in the web.config file (combined with LDAP setting, this enables the bypass)
-
Check LDAP configuration for anonymous authenticationExamine the LDAP authentication settings configured for eSOMS. Look for the anonymous authentication setting in the LDAP configuration.Affected if LDAP is configured to allow anonymous authentication (combined with web.config keys, this enables the bypass)
-
Confirm both conditions are presentReview findings from both the web.config inspection and LDAP configuration check together.Affected if Both LDAP anonymous authentication is enabled AND sensitive key values exist in web.config - only when both conditions are true is the system vulnerable
A system is affected only if it runs eSOMS version 6.0.2 AND has LDAP anonymous authentication enabled AND contains sensitive key values in the web.config file - all three conditions must be met.
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 dataDisable anonymous authentication in the LDAP configuration and audit/remove or properly secure the specific sensitive key values in the eSOMS web.config file.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14805 — 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-14805 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