dbcve.org
HTTP ServerWeb server / proxy · Oracle

CVE-2015-3195

MEDIUM · 5.3 CVSS v3.1 Published 2015-12-06
Fix available
A fix is available. Upgrade to 0.9.8zh / 1.0.0t or later.
See remediation →
62/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
The ASN1_TFLG_COMBINE implementation in crypto/asn1/tasn_dec.c in OpenSSL before 0.9.8zh, 1.0.0 before 1.0.0t, 1.0.1 before 1.0.1q, and 1.0.2 before 1.0.2e mishandles errors caused by malformed X509_ATTRIBUTE data, which allows remote attackers to obtain sensitive information from process memory by triggering a decoding failure in a PKCS#7 or CMS application.

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

OpenSSL contains a flaw in the ASN1_TFLG_COMBINE implementation in crypto/asn1/tasn_dec.c where error handling fails properly when decoding malformed X509_ATTRIBUTE data within PKCS#7 or CMS structures. This causes decoding failures that can expose sensitive process memory contents to remote attackers.

MitigationUpgrade OpenSSL to version 0.9.8zh, 1.0.0t, 1.0.1q, 1.0.2e or later to patch the ASN.1 parsing error handling. Alternatively, ensure PKCS#7/CMS parsing operations handle errors gracefully and do not expose memory contents on decode failures.

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
HTTP ServerWeb server / proxy
Affected:= 11.5.10.2
LinuxOperating system
Affected:= 5= 6= 7
OpenSSLFramework / library
Affected:< 0.9.8zh>= 1.0.0, < 1.0.0t>= 1.0.1, < 1.0.1q>= 1.0.2, < 1.0.2e
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.2= 7.3= 7.4= 7.6= 7.7
Enterprise Linux Server TusOperating system
Affected:= 7.2= 7.3= 7.6= 7.7
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0= 7.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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. Identify the installed OpenSSL version
    Run `openssl version` or check the library file (e.g., /usr/lib/libssl.so.1.0.1e on RHEL, or use `rpm -q openssl` / `dpkg -l libssl` depending on OS)
    Affected if The version is less than 0.9.8zh, OR between 1.0.0 and 1.0.0t (excluding t), OR between 1.0.1 and 1.0.1q (excluding q), OR between 1.0.2 and 1.0.2e (excluding e)
  2. Confirm the OpenSSL library file path
    Run `ldd <binary> | grep ssl` on any SSL/TLS enabled service, or check `openssl version -a` for compile flags and library path
    Affected if The linked OpenSSL library matches an affected version from step 1
  3. Determine if PKCS#7 or CMS parsing is in use
    Review application logs, configurations, or code that handles PKCS#7 (multipart signed data) or CMS (Cryptographic Message Syntax) encoded data, as these are the code paths that trigger the vulnerable ASN.1 parsing
    Affected if The environment processes PKCS#7 or CMS data structures (common in S/MIME email, code signing, or SSL certificate verification)
  4. Check for services accepting external PKCS#7/CMS input
    Audit services that accept PKCS#7 or CMS input from untrusted sources, such as email servers, document signing services, or SSL termination proxies
    Affected if Such services exist and use an affected OpenSSL version

You are affected if your installed OpenSSL version falls within the vulnerable ranges AND your environment processes PKCS#7 or CMS data structures.

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
Upgrade available Upgrade to 0.9.8zh / 1.0.0t / 1.0.1q or later
Fixed in 0.9.8zh1.0.0t1.0.1q
Interim mitigation

Upgrade OpenSSL to version 0.9.8zh, 1.0.0t, 1.0.1q, 1.0.2e or later to patch the ASN.1 parsing error handling. Alternatively, ensure PKCS#7/CMS parsing operations handle errors gracefully and do not expose memory contents on decode failures.

Fix this in HTTP Server 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 the upgrade done

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-2015-3195 — 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-2015-3195 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