dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2019-9628

HIGH · 7.5 CVSS v3.1 Published 2019-04-11
Fix available
A fix is available. Upgrade to 3.0.4 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
The XMLTooling library all versions prior to V3.0.4, provided with the OpenSAML and Shibboleth Service Provider software, contains an XML parsing class. Invalid data in the XML declaration causes an exception of a type that was not handled properly in the parser class and propagates an unexpected exception type.

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

The XMLTooling library (versions prior to V3.0.4) used by OpenSAML and Shibboleth Service Provider contains an XML parsing class that improperly handles invalid data in XML declarations. When malformed XML declarations are processed, an exception of an unhandled type is thrown, causing unexpected exception propagation that can lead to denial of service or unpredictable application behavior.

MitigationUpgrade the XMLTooling library to version 3.0.4 or later, which includes proper exception handling for invalid XML declaration data. This typically involves updating the OpenSAML or Shibboleth SP installation to a version that bundles the fixed 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:= 14.04= 16.04= 18.04= 18.10
XmltoolingApplication
Affected:< 3.0.4
LeapOperating system
Affected:= 15.0= 42.3

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.1/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. Check your operating system version
    Run 'lsb_release -a' on Ubuntu or 'cat /etc/os-release' on openSUSE to identify the installed OS version
    Affected if The OS is Ubuntu 14.04, 16.04, 18.04, 18.10 or openSUSE Leap 15.0 or 42.3
  2. Locate the XMLTooling library
    Search for libxmltooling or xmltooling files using 'find /usr -name "*xmltooling*" 2>/dev/null' or check package manager with 'dpkg -l | grep xmltooling' (Ubuntu) or 'rpm -qa | grep xmltooling' (openSUSE)
    Affected if XMLTooling library is installed on the system
  3. Determine the installed XMLTooling version
    Run 'dpkg -l | grep xmltooling' on Debian-based systems or 'rpm -qi xmltooling' on RPM-based systems, or examine the library file directly with 'strings <path_to_library> | grep -i version'
    Affected if The version number is less than 3.0.4 or cannot be determined (indicating an older unpatched version)
  4. Check for OpenSAML or Shibboleth SP installation
    Search for opensaml or shibboleth components using 'find / -name "*opensaml*" -o -name "*shibboleth*" 2>/dev/null' or check package manager with 'dpkg -l | grep -E "opensaml|shibboleth"'
    Affected if OpenSAML or Shibboleth Service Provider is installed and linked to the vulnerable XMLTooling library
  5. Verify if XML parsing with external XML declarations is in use
    Review application logs and configuration for XML processing pipelines, particularly those that accept XML input from untrusted sources or process SAML metadata
    Affected if The application processes XML declarations from external or untrusted sources using the affected XMLTooling library

Your environment is affected if you are running Ubuntu 14.04-18.10 or openSUSE Leap 15.0/42.3 with XMLTooling library versions prior to 3.0.4 that are used by OpenSAML or Shibboleth SP to process XML declarations.

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 3.0.4 or later
Fixed in 3.0.4
Interim mitigation

Upgrade the XMLTooling library to version 3.0.4 or later, which includes proper exception handling for invalid XML declaration data. This typically involves updating the OpenSAML or Shibboleth SP installation to a version that bundles the fixed library.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
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,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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