usn-2211-1
Vulnerability from osv_ubuntu
Published
2014-05-14 14:20
Modified
2026-04-22 07:36
Summary
libxfont vulnerabilities
Details

Ilja van Sprundel discovered that libXfont incorrectly handled font metadata file parsing. A local attacker could use this issue to cause libXfont to crash, or possibly execute arbitrary code in order to gain privileges. (CVE-2014-0209)

Ilja van Sprundel discovered that libXfont incorrectly handled X Font Server replies. A malicious font server could return specially-crafted data that could cause libXfont to crash, or possibly execute arbitrary code. This issue only affected Ubuntu 10.04 LTS, Ubuntu 12.04 LTS, Ubuntu 12.10 and Ubuntu 13.10. (CVE-2014-0210, CVE-2014-0211)

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2014-0209",
              "severity": [
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:14.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "libxfont1",
            "binary_version": "1:1.4.7-1ubuntu0.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:14.04:LTS",
        "name": "libxfont",
        "purl": "pkg:deb/ubuntu/libxfont@1:1.4.7-1ubuntu0.1?arch=source\u0026distro=trusty"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1:1.4.7-1ubuntu0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1:1.4.6-1",
        "1:1.4.6-1ubuntu1",
        "1:1.4.7-1"
      ]
    }
  ],
  "aliases": [],
  "details": "Ilja van Sprundel discovered that libXfont incorrectly handled font\nmetadata file parsing. A local attacker could use this issue to cause\nlibXfont to crash, or possibly execute arbitrary code in order to gain\nprivileges. (CVE-2014-0209)\n\nIlja van Sprundel discovered that libXfont incorrectly handled X Font\nServer replies. A malicious font server could return specially-crafted data\nthat could cause libXfont to crash, or possibly execute arbitrary code.\nThis issue only affected Ubuntu 10.04 LTS, Ubuntu 12.04 LTS, Ubuntu 12.10\nand Ubuntu 13.10. (CVE-2014-0210, CVE-2014-0211)\n",
  "id": "USN-2211-1",
  "modified": "2026-04-22T07:36:31Z",
  "published": "2014-05-14T14:20:12Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-2211-1"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2014-0209"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2014-0210"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2014-0211"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "libxfont vulnerabilities",
  "upstream": [
    "UBUNTU-CVE-2014-0209",
    "UBUNTU-CVE-2014-0210",
    "UBUNTU-CVE-2014-0211"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.