CVE-2024-25371VulnerabilityPublished 10 Jan 2025Updated 14 Jan 2025

CVE-2024-25371: gramine · n/a

Affects gramineSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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 10 Jan 2025
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 2026-10-26.

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 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

Affected software

Product	Affected	Fixed in
GitHubgramineproject/gramine`pkg:github/gramineproject/gramine`Other threats	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-25371, organizations should first monitor official Gramine project channels for patches or updates addressing the interface mismatch. Until a patch is available, deploying network-level protections such as firewalls and intrusion prevention systems to restrict access to Gramine-exposed services can reduce exposure. Implementing strict network segmentation to isolate trusted execution environments from untrusted networks is recommended. Additionally, monitoring application and system logs for abnormal signal handling or unexpected process terminations can provide early warning of exploitation attempts. Where feasible, consider deploying fallback or redundancy mechanisms to maintain availability if Gramine-based applications crash. Security teams should also conduct thorough testing of Gramine deployments to identify any custom configurations that might exacerbate the vulnerability. Finally, coordinate with cloud providers or vendors using Gramine to ensure timely updates and shared threat intelligence.

Description

Gramine before a390e33e16ed374a40de2344562a937f289be2e1 suffers from an Interface vulnerability due to mismatching SW signals vs HW exceptions.

Impact

The primary impact of CVE-2024-25371 is a denial-of-service condition that can disrupt availability of applications running within Gramine-based trusted execution environments. Organizations relying on Gramine to secure sensitive workloads in cloud or edge environments may experience service outages or application crashes, potentially affecting business continuity and operational reliability. Since the vulnerability does not affect confidentiality or integrity, data breaches or unauthorized data modifications are not expected. However, the loss of availability in security-critical environments could undermine trust in protected applications and delay critical processing tasks. The ease of remote exploitation without authentication increases the risk of widespread attacks, especially in environments where Gramine is exposed to untrusted networks. Although no known exploits exist yet, the vulnerability's presence in a niche but growing technology stack means targeted attackers could develop exploits to disrupt secure enclaves or cloud services. This could have cascading effects on organizations using Gramine for confidential computing, including cloud service providers, financial institutions, and government agencies.

References

Community reviews

Loading reviews…