Ubuntu LinuxOperating system · Canonical

CVE-2016-4574

HIGH · 7.5 CVSS v3.0 Published 2016-06-13
Fix available
A fix is available. Upgrade to after 1.3.3 or later.
See remediation →
84/100
Remediation priority · High
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
Off-by-one error in the append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.4 allows remote attackers to cause a denial of service (out-of-bounds read) via invalid utf-8 encoded data. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-4356.

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

Off-by-one error in append_utf8_value function in dn.c in Libksba before 1.3.4 allows out-of-bounds read via invalid UTF-8 encoded data in the Distinguished Name (DN) decoder. This is an incomplete fix for CVE-2016-4356, where the initial patch did not fully address the boundary condition. Remote attackers can trigger this by presenting malformed X.509 certificate data with specially crafted UTF-8 sequences.

MitigationUpgrade to Libksba version 1.3.4 or later to obtain the complete fix. Audit all applications and services that link against Libksba to ensure they are rebuilt against the updated library.

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
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 15.10= 16.04
LibksbaApplication
Affected:<= 1.3.3
LeapOperating system
Affected:= 42.1
OpensuseOperating system
Affected:= 13.2

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
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Libksba is installed
    Run 'dpkg -l | grep libksba' on Debian/Ubuntu, or 'rpm -qa | grep -i ksba' on RHEL/SUSE, or 'ls /usr/lib*/libksba*' to locate the library file
    Affected if Libksba is not installed or no library file is found - the vulnerability does not apply
  2. Check the installed Libksba version
    Run 'ksba-config --version' if available, or check the library file version with 'objdump -p /usr/lib*/libksba.so.8 | grep Version' or 'dpkg -s libksba'
    Affected if Version is 1.3.3 or lower, or the package version indicates anything before 1.3.4 - the system is potentially affected
  3. Identify applications using Libksba
    Run 'ldd /path/to/binary | grep ksba' on suspected binaries, or 'find /usr -name "*.so*" -exec ldd {} \; 2>/dev/null | grep -i ksba' to find linked binaries, or check GnuPG with 'gpg --version' and verify it links to libksba
    Affected if Applications that parse X.509 certificates or handle DNs are linked against a vulnerable Libksba version - the flaw can be triggered
  4. Determine if certificate processing is in use
    Review logs or configuration for services accepting or verifying X.509 certificates (TLS/SSL services, S/MIME, code signing), or check for certificates in PEM/DER format being processed
    Affected if The environment processes X.509 certificates with UTF-8 encoded Subject/Issuer DNs - malformed certificates could trigger the out-of-bounds read

A system is affected if it runs Libksba version 1.3.3 or earlier AND processes X.509 certificates containing specially crafted UTF-8 sequences in Distinguished Names.

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 a release after 1.3.3
Interim mitigation

Upgrade to Libksba version 1.3.4 or later to obtain the complete fix. Audit all applications and services that link against Libksba to ensure they are rebuilt against the updated library.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4574 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4574 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