dbcve.org
FedoraOperating system · Fedoraproject

CVE-2015-8106

HIGH · 7.8 CVSS v3.0 Published 2016-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Format string vulnerability in the CmdKeywords function in funct1.c in latex2rtf before 2.3.10 allows remote attackers to execute arbitrary code via format string specifiers in the \keywords command in a crafted TeX file.

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

Format string vulnerability in latex2rtf's CmdKeywords function allows attackers to inject format string specifiers into the \keywords command in a crafted TeX file, potentially executing arbitrary code through improper handling of user input passed to format string functions.

MitigationUpdate latex2rtf to version 2.3.10 or later. Avoid processing untrusted TeX files with vulnerable versions until patched.

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
Affected:= 22= 23= 24
Latex2rtfApplication
Affected:= 2.3.8

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 if latex2rtf is installed
    Run command: which latex2rtf or rpm -qa | grep latex2rtf (on Fedora/RHEL)
    Affected if latex2rtf command is found on the system
  2. Determine installed latex2rtf version
    Run: latex2rtf --version 2>&1 | head -1 and note the version number displayed
    Affected if Version displayed is 2.3.8 or if running on Fedora 22/23/24 with any latex2rtf version
  3. Identify TeX files using the keywords command
    Search for .tex files containing \keywords{ using: grep -r '\\keywords{' /path/to/search
    Affected if TeX files with \keywords command exist and are processed by latex2rtf
  4. Verify vulnerability trigger condition
    The vulnerability triggers when latex2rtf processes a TeX file containing format string specifiers (such as %s, %n, %x) within the \keywords{} argument
    Affected if A crafted TeX file with malicious format string specifiers in \keywords is processed by the vulnerable latex2rtf version

User is affected if latex2rtf version 2.3.8 is installed, or if latex2rtf from Fedora 22/23/24 processes untrusted TeX files containing the \keywords command with embedded format string specifiers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update latex2rtf to version 2.3.10 or later. Avoid processing untrusted TeX files with vulnerable versions until patched.

Fix this in Fedora 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 help mitigating

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-8106 — 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-8106 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