ghsa-g8qj-jv5h-78cp
Vulnerability from github
Published
2025-03-11 15:31
Modified
2025-04-03 00:31
Severity ?
Details
An out of bounds write exists in FreeType versions 2.13.0 and below when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.
{ affected: [], aliases: [ "CVE-2025-27363", ], database_specific: { cwe_ids: [ "CWE-787", ], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2025-03-11T14:15:25Z", severity: "HIGH", }, details: "An out of bounds write exists in FreeType versions 2.13.0 and below when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.", id: "GHSA-g8qj-jv5h-78cp", modified: "2025-04-03T00:31:31Z", published: "2025-03-11T15:31:00Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2025-27363", }, { type: "WEB", url: "https://lists.debian.org/debian-lts-announce/2025/03/msg00030.html", }, { type: "WEB", url: "https://www.facebook.com/security/advisories/cve-2025-27363", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/13/1", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/13/11", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/13/12", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/13/2", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/13/3", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/13/8", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/14/1", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/14/2", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/14/3", }, { type: "WEB", url: "http://www.openwall.com/lists/oss-security/2025/03/14/4", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", type: "CVSS_V3", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.