CVE-2014-6136
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 · uneditedIBM Security AppScan Standard 8.x and 9.x before 9.0.1.1 FP1 supports unencrypted sessions, which allows remote attackers to obtain sensitive information by sniffing the network.
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 confidenceIBM Security AppScan Standard 8.x and 9.x versions before 9.0.1.1 FP1 supports unencrypted (non-HTTPS) sessions, allowing sensitive data to be transmitted in plaintext across the network where it can be captured by sniffing 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= 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.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Verify AppScan Standard versionOpen the application and navigate to Help > About, or check the installed program version through Windows Add/Remove Programs or the application's installation directory for version informationAffected if The installed version is 8.0.0.0 through 8.8.0.0, or 9.0.0.0 (all versions before 9.0.1.1 FP1)
-
Check protocol configurationExamine the application's configuration settings for session and communication protocol settings. Look for options related to HTTP/HTTPS, SSL, or encryption settings in the application preferences or administration panelAffected if The application is configured to allow or default to non-HTTP (plaintext) connections
-
Inspect server or service settingsIf AppScan is running as a server service, check the server configuration files or administration console for transport security settings. Verify whether HTTPS/SSL is enforced or optionalAffected if SSL/TLS encryption is not enabled or is set to optional/disabled
-
Test network communicationUse network capture tools to observe traffic between the AppScan client and server (if applicable). Attempt to initiate a session and capture the network packets to check if data is transmitted in plaintextAffected if Sensitive session data is transmitted in plaintext without TLS/SSL encryption
You are affected if running AppScan Standard version 8.x or 9.x before 9.0.1.1 FP1 and the application is configured to use unencrypted (non-HTTPS) sessions for communication.
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 dataEnable SSL/TLS encryption for all sessions by configuring the application to use HTTPS and enforcing secure communication channels.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6136 — 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-2014-6136 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