VulnerabilityPublished 22 Sep 2022Updated 27 May 2025

CVE-2022-35024: OTFCC · Memory Buffer Overflow

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Monitor for updates from the OTFCC project or any software vendors that incorporate OTFCC components and apply patches promptly once available.
Implement strict input validation and sandboxing for applications that process untrusted font or document files to limit the impact of malformed inputs triggering the vulnerability.
Employ endpoint protection solutions that can detect abnormal application crashes or memory violations to quickly identify exploitation attempts.
Educate users about the risks of opening untrusted or unexpected files, especially from email attachments or web downloads, to reduce the likelihood of user interaction-based exploitation.
For organizations developing software that uses OTFCC, conduct thorough code reviews and fuzz testing focused on memory handling in assembly routines to identify and remediate similar issues proactively.
Use application whitelisting and restrict execution privileges to minimize the attack surface and prevent unauthorized code execution that could leverage this vulnerability.

Description

OTFCC commit 617837b was discovered to contain a segmentation violation via /multiarch/memmove-vec-unaligned-erms.S.

Impact

For European organizations, the primary impact of CVE-2022-35024 is the potential for denial of service conditions in software that incorporates the vulnerable OTFCC component or its affected assembly routines. Since the vulnerability does not impact confidentiality or integrity, data breaches or unauthorized data modifications are unlikely. However, availability disruptions can affect critical services, especially if the vulnerable code is part of infrastructure software, font rendering engines, or other widely used libraries. Organizations relying on software that uses OTFCC for font handling or related processing may experience application crashes or system instability if exploited. This could lead to service interruptions, user dissatisfaction, and operational downtime. The requirement for user interaction (UI:R) means that exploitation would likely need a user to open a malicious file or interact with crafted content, which could be delivered via email, web, or other vectors. This reduces the risk of automated widespread exploitation but still poses a threat in targeted attacks or phishing scenarios. European organizations with high dependency on desktop publishing, document processing, or specialized software that integrates OTFCC components should be particularly vigilant.

Summary

CVE-2022-35024 is a medium severity vulnerability identified in the OTFCC project, specifically related to a segmentation violation caused by the assembly file /multiarch/memmove-vec-unaligned-erms.S. The vulnerability is classified under CWE-119, which corresponds to a classic buffer overflow or improper memory handling issue. The segmentation violation indicates that the code attempts to access memory incorrectly, potentially leading to a crash or denial of service. The CVSS 3.1 base score is 6.5, reflecting a network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The impact is limited to availability (A:H), with no confidentiality or integrity impact. This suggests that exploitation would cause a denial of service by crashing the affected process or system component. No known exploits are currently in the wild, and no specific affected product versions or vendors are identified, which implies this vulnerability is in a component or codebase (OTFCC) that may be embedded or used in various software projects. The lack of patch links indicates that a fix may not yet be publicly available or that the vulnerability is newly disclosed. The technical root cause is a segmentation fault triggered by a memory operation in an assembly routine responsible for optimized memory movement on certain architectures, which may be triggered by crafted input or usage patterns.

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Jul 2025, 04:09 UTC

WeaknessesCWE-119

Technical details

References

Community reviews

Related threats