Debian LinuxOperating system · Debian
CVE-2016-4348
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 · uneditedThe _rsvg_css_normalize_font_size function in librsvg 2.40.2 allows context-dependent attackers to cause a denial of service (stack consumption and application crash) via circular definitions in an SVG document.
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 confidenceA stack consumption vulnerability exists in librsvg 2.40.2 where the _rsvg_css_normalize_font_size function lacks proper recursion guards, allowing malicious SVG documents with circular font-size definitions to exhaust the stack and crash the application.
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
Debian LinuxOperating system
= 8.0<= 2.40.1= 42.1= 13.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if librsvg is installedRun 'dpkg -l | grep librsvg' on Debian/Ubuntu, 'rpm -qa | grep librsvg' on RHEL/SUSE, or check for shared library files in /usr/lib/ and /usr/lib64/Affected if librsvg package or shared library files are present on the system
-
Determine installed librsvg versionRun 'rsvg-convert --version' or 'dpkg -s librsvg-2-2' on Debian, 'rpm -qi librsvg' on SUSE/RHEL, or use 'pkg-config --modversion librsvg-2.0'Affected if Version returned is 2.40.2 or lower, or matches Debian 8.0, openSUSE 42.1, or openSUSE 13.2 packages
-
Identify applications using librsvgCheck which applications link against librsvg by running 'ldd $(which eog)' or 'ldd $(which nautilus)' for GNOME file managers, or search for processes that load librsvg-2.soAffected if Applications like EOG, Nautilus, or other SVG-rendering software are in use
-
Verify SVG processing is possibleTest if librsvg can process SVG files by running 'rsvg-convert test.svg > test.png' with a sample SVG file, or check if thumbnail previews of SVG files work in file managersAffected if SVG files can be rendered or thumbnails generated on the system
A system is affected if librsvg version 2.40.2 or lower is installed and any application uses it to render or process SVG files, allowing malicious SVGs with circular font-size definitions to trigger stack exhaustion.
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 dataUpgrade librsvg to a version that implements recursion limits or cycle detection in the _rsvg_css_normalize_font_size function, and sanitize untrusted SVG input before processing.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4348 — 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-2016-4348 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