FedoraOperating system · Fedoraproject
CVE-2019-20446
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 · uneditedIn xml.rs in GNOME librsvg before 2.46.2, a crafted SVG file with nested patterns can cause denial of service when passed to the library for processing. The attacker constructs pattern elements so that the number of final rendered objects grows exponentially.
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 · moderate confidenceA denial of service vulnerability exists in GNOME librsvg's XML processing (xml.rs) where specially crafted SVG files containing nested pattern elements can trigger exponential growth in the number of rendered objects. This causes excessive resource consumption leading to service unavailability when the malicious SVG is processed.
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
FedoraOperating system
= 30= 31
Debian LinuxOperating system
= 9.0
Ubuntu LinuxOperating system
= 16.04= 18.04< 2.40.21>= 2.42.0, < 2.42.8>= 2.44.0, < 2.44.16= 15.1all versionsCVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify librsvg versionRun 'rpm -qa | grep librsvg' (Fedora/RHEL) or 'dpkg -l | grep librsvg' (Debian/Ubuntu) or 'zypper se librsvg' (OpenSUSE) to list installed librsvg packages and their versionsAffected if The installed version is < 2.40.21, OR >= 2.42.0 and < 2.42.8, OR >= 2.44.0 and < 2.44.16
-
Find applications using librsvgRun 'ldd /usr/bin/rsvg-convert 2>/dev/null' or check application dependencies with 'ldd <application_binary>' to confirm they link against librsvgAffected if Applications depend on librsvg and process SVG files
-
Check for SVG processing servicesReview running services and applications that handle image conversion, thumbnail generation, or SVG rendering using commands like 'ps aux' and examine configuration files for SVG-related processingAffected if Services or applications process SVG files, particularly from user uploads or external sources
-
Verify NetApp Active IQ Unified ManagerIf the environment contains NetApp Active IQ Unified Manager, note that all versions are affected regardless of librsvg versionAffected if NetApp Active IQ Unified Manager is installed and processes SVG content
The environment is affected if librsvg version falls within the vulnerable ranges AND applications using librsvg process SVG files, particularly untrusted ones.
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 data2.40.212.42.82.44.16
Update librsvg to version 2.46.2 or later to obtain the patch. Until then, avoid processing untrusted SVG files with the library.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20446 — 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-2019-20446 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