CVE Tools

CVE-2011-5244

No known exploitation. EPSS puts it in the 88th percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

What it is

From the CVE record

Multiple off-by-one errors in the (1) token and (2) linetoken functions in backend/dvi/mdvi-lib/afmparse.c in t1lib, as used in teTeX 3.0.x, GNOME evince, and possibly other products, allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a DVI file containing a crafted Adobe Font Metrics (AFM) file, different vulnerabilities than CVE-2010-2642 and CVE-2011-0433.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS88th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

3.4% chance of exploitation activity in the next 30 days, which ranks it in the 88th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 4966 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updated
  3. Publishedweakness classified

Affected products

And 1 more affected product. See all after sign-in

Technical detail

AV:N/AC:M/Au:N/C:P/I:P/A:P

Scored 6.8 by NVD.

How it is reached

  • Access Vector NetworkExploitable remotely over the network
  • Access Complexity MediumSome conditions must be met
  • Authentication NoneNo authentication required

Impact if exploited

  • Confidentiality PartialSome information is disclosed
  • Integrity PartialSome data can be modified
  • Availability PartialReduced performance or service disruption

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Evince, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store