# CVE-2010-0421: Denial of service in n/a > Attackers can crash applications using Pango by providing a crafted font file, requiring user interaction to load the malicious font. - **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 18 Mar 2010 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2010-0421, DSA-2019-1, GHSA-77cq-2r3w-6xhj, RHSA-2010:0140 ## What is CVE-2010-0421? CVE-2010-0421 is a medium-severity denial of service vulnerability in n/a, published on 18 Mar 2010. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description Array index error in the hb_ot_layout_build_glyph_classes function in pango/opentype/hb-ot-layout.cc in Pango before 1.27.1 allows context-dependent attackers to cause a denial of service (application crash) via a crafted font file, related to building a synthetic Glyph Definition (aka GDEF) table by using this font's charmap and the Unicode property database. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2010-0421? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pango` | Red Hat:enterprise_linux:3::as | All versions | 0:1.2.5-10 | | `pango-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.2.5-10 | | `pango-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.2.5-10 | | `pango` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.2.5-10 | | `pango-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.2.5-10 | | `pango-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.2.5-10 | | `pango` | Red Hat:enterprise_linux:3::es | All versions | 0:1.2.5-10 | | `pango-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.2.5-10 | | `pango-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.2.5-10 | | `pango` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.2.5-10 | | `pango-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.2.5-10 | | `pango-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.2.5-10 | | `evolution28-pango` | Red Hat:enterprise_linux:4::as | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.14.9-13.el4_8 | | `pango` | Red Hat:enterprise_linux:4::as | All versions | 0:1.6.0-16.el4_8 | | `pango-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.6.0-16.el4_8 | | `pango-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.6.0-16.el4_8 | | `evolution28-pango` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.14.9-13.el4_8 | | `pango` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.6.0-16.el4_8 | | `pango-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.6.0-16.el4_8 | | `pango-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.6.0-16.el4_8 | | `evolution28-pango` | Red Hat:enterprise_linux:4::es | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.14.9-13.el4_8 | | `pango` | Red Hat:enterprise_linux:4::es | All versions | 0:1.6.0-16.el4_8 | | `pango-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.6.0-16.el4_8 | | `pango-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.6.0-16.el4_8 | | `evolution28-pango` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.14.9-13.el4_8 | | `evolution28-pango-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.14.9-13.el4_8 | | `pango` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.6.0-16.el4_8 | | `pango-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.6.0-16.el4_8 | | `pango-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.6.0-16.el4_8 | | `pango` | Red Hat:enterprise_linux:5::client | All versions | 0:1.14.9-8.el5 | | `pango-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.14.9-8.el5 | | `pango` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.14.9-8.el5 | | `pango-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.14.9-8.el5 | Products: Gnome Pango. ## How do I fix CVE-2010-0421? Upgrade to a fixed version. ## Is CVE-2010-0421 being exploited? There is no known exploitation of CVE-2010-0421 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2011-0020](https://insights.sbomify.com/CVE-2011-0020/): Memory corruption in n/a (high 7.6) - [CVE-2011-0064](https://insights.sbomify.com/CVE-2011-0064/): Null dereference in n/a (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2010-0421 and fix it if it is affected. What it is: CVE-2010-0421 is a medium-severity denial of service vulnerability in n/a, published on 18 Mar 2010. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2010-0421 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2010-0421/ (Markdown: https://insights.sbomify.com/CVE-2010-0421/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0421 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0421 - OSV: https://osv.dev/vulnerability/CVE-2010-0421 --- From sbomify Insights: https://insights.sbomify.com/CVE-2010-0421/ Summaries are generated and may contain mistakes; the official description above is the record.