dbcve.org
Security AppscanApplication · Ibm

CVE-2014-8918

MEDIUM · 5.8 CVSS v2.0 Published 2015-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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
IBM Security AppScan Standard 8.x and 9.x before 9.0.1.1 FP1 does not properly verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

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 confidence

IBM Security AppScan Standard versions 8.x and 9.x before 9.0.1.1 FP1 fails to properly verify X.509 certificates from SSL servers during secure connections, enabling man-in-the-middle attackers to spoof legitimate servers using crafted certificates and intercept sensitive transmitted data.

MitigationUpgrade IBM Security AppScan Standard to version 9.0.1.1 FP1 or later, which implements proper X.509 certificate chain validation to prevent MITM attacks.

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
Security AppscanApplication
Affected:= 8.0.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.5.0.0= 8.5.0.1= 8.6.0.0= 8.6.0.1= 8.7.0.0= 8.7.0.1= 8.8.0.0= 9.0.0.0

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/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. Check installed AppScan version
    Open IBM Security AppScan Standard and navigate to Help > About, or locate the version in the installation directory
    Affected if Version is 8.0.0.0, 8.0.0.1, 8.0.0.2, 8.0.0.3, 8.5.0.0, 8.5.0.1, 8.6.0.0, 8.6.0.1, 8.7.0.0, 8.7.0.1, 8.8.0.0, or 9.0.0.0
  2. Confirm SSL/TLS scanning is used
    Verify that AppScan is configured to scan or test HTTPS endpoints - this is the default scanning behavior when scanning secure web applications
    Affected if The application makes SSL/TLS connections to target servers, which is the default behavior for scanning HTTPS sites
  3. Identify if custom SSL trust settings exist
    Check AppScan options for any manual certificate trust configuration or SSL settings that may affect certificate validation
    Affected if Custom SSL settings are configured that bypass default certificate validation

If the installed version is 8.x or 9.0.0.0 and AppScan is used to scan HTTPS endpoints, the certificate validation flaw is present.

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

Upgrade IBM Security AppScan Standard to version 9.0.1.1 FP1 or later, which implements proper X.509 certificate chain validation to prevent MITM attacks.

Fix this in Security Appscan Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8918 — 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-2014-8918 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