Skip to content
Noroxi
CVE-2011-0020· NVD / CVE Program· CNA redhat

Heap-based buffer overflow in the pango_ft2_font_render_box_glyph function in pango/pangoft2-render.c in libpango in Pango 1.28.3 and earlie

Heap-based buffer overflow in the pango_ft2_font_render_box_glyph function in pango/pangoft2-render.c in libpango in Pango 1.28.3 and earlier, when the FreeType2 backend is enabled, allows user-assisted remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted font file, related to the glyph box for an FT_Bitmap object.

HighCVSS 7.6 · v2.0—Proof of concept Fix available
Published
Jan 24, 2011
Updated
Jun 16, 2026
EPSS
18.9% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
30 / 40 · 7.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
6 / 30 · 18.9%

Affected systems

VendorProduct
pangopango
gnomepango

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnome pangoup to 1.28.3 inclusive
  • gnome pango1.28.0
  • gnome pango1.28.1
  • gnome pango1.28.2
  • pango pango0.20
  • pango pango0.21
  • pango pango0.22
  • pango pango0.23
  • pango pango0.24
  • pango pango0.25
  • pango pango0.26
  • pango pango1.0
  • pango pango1.1
  • pango pango1.10
  • pango pango1.11
  • pango pango1.12
  • pango pango1.13
  • pango pango1.14
  • pango pango1.15
  • pango pango1.16

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12pango1.0before 1.28.3-1+squeeze11.28.3-1+squeeze1
openSUSE:Tumbleweedpangobefore 1.40.3-1.11.40.3-1.1
Red Hat:enterprise_linux:4::asevolution28-pangobefore 0:1.14.9-13.el4_100:1.14.9-13.el4_10
Red Hat:enterprise_linux:4::asevolution28-pango-debuginfobefore 0:1.14.9-13.el4_100:1.14.9-13.el4_10
Red Hat:enterprise_linux:4::asevolution28-pango-develbefore 0:1.14.9-13.el4_100:1.14.9-13.el4_10
Red Hat:enterprise_linux:5::serverpangobefore 0:1.14.9-8.el5_6.20:1.14.9-8.el5_6.2
Red Hat:enterprise_linux:5::serverpango-debuginfobefore 0:1.14.9-8.el5_6.20:1.14.9-8.el5_6.2
Red Hat:enterprise_linux:5::serverpango-develbefore 0:1.14.9-8.el5_6.20:1.14.9-8.el5_6.2
Red Hat:enterprise_linux:6::clientpangobefore 0:1.28.1-3.el6_0.30:1.28.1-3.el6_0.3
Red Hat:enterprise_linux:6::clientpango-debuginfobefore 0:1.28.1-3.el6_0.30:1.28.1-3.el6_0.3
Red Hat:enterprise_linux:6::clientpango-develbefore 0:1.28.1-3.el6_0.30:1.28.1-3.el6_0.3

Other highest-scoring records for the same primary product.

  • CVE-2009-1194Integer overflow in the pango_glyph_string_set_size function in pango/glyphstring.c in Pango before 1.24 allows context-dependent attackers
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:pango1.01.28.3-1+squeeze1 · Debian:12Package registry (OSV)
opensuse:pango1.40.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:evolution28-pango0:1.14.9-13.el4_10 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:evolution28-pango-debuginfo0:1.14.9-13.el4_10 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:evolution28-pango-devel0:1.14.9-13.el4_10 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:pango0:1.14.9-8.el5_6.2 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:pango-debuginfo0:1.14.9-8.el5_6.2 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:pango-devel0:1.14.9-8.el5_6.2 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entryremote2011-01-18

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-7 d
  2. Published
  3. TodaySep 30, 2026+5728 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
C · data can be read
Integrity
C · data or configuration can be modified
Availability
C · the service can be disrupted
Attack complexity
High
Confidentiality impact
C
Integrity impact
C
Availability impact
C

CVSS vector

AV:N/AC:H/Au:N/C:C/I:C/A:C

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records