CVE-2024-22778VulnerabilityPublished 21 Feb 2024Updated 6 Nov 2024

CVE-2024-22778: codimd · n/a

Affects codimdSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.5.2 soon.

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.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.5.2

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 21 Feb 2024
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

Upgrade hackmdio/codimd to 2.5.2.

Affected software

Product	Affected	Fixed in
GitHubhackmdio/codimd`pkg:github/hackmdio/codimd`Other threats	Affected <2.5.2	Fixed in 2.5.2

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

AI-suggested

1. Upgrade HackMD/CodiMD to version 2.5.2 or later as soon as the patch is available to eliminate the vulnerability. 2. Until patching is complete, restrict network access to HackMD/CodiMD instances using firewalls or VPNs to limit exposure to trusted users only. 3. Implement rate limiting and request throttling on the application or web server level to reduce the risk of resource exhaustion attacks. 4. Monitor application logs and network traffic for unusual patterns indicative of DoS attempts, such as spikes in malformed requests or connection attempts. 5. Consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious traffic targeting HackMD/CodiMD endpoints. 6. Educate system administrators and users about the vulnerability and the importance of timely patching. 7. Regularly back up critical documentation data to minimize impact in case of service disruption. 8. Review and harden server configurations to reduce attack surface, including disabling unnecessary services and enforcing strong access controls.

Description

HackMD CodiMD <2.5.2 is vulnerable to Denial of Service.

Impact

The primary impact of CVE-2024-22778 is the disruption of service availability, which can halt collaborative documentation workflows critical to development, education, and research teams. Denial of service attacks can lead to operational downtime, loss of productivity, and potential reputational damage for organizations relying on HackMD/CodiMD. Since the vulnerability requires no authentication or user interaction, it can be exploited by any remote attacker with network access, increasing the attack surface. The absence of confidentiality or integrity impact means data leakage or tampering is not a concern here, but availability loss can still have cascading effects on dependent processes and teams. Organizations with public-facing HackMD/CodiMD instances are particularly vulnerable to external attacks, while internal deployments may be at risk from insider threats or lateral movement. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future attacks, especially as awareness of the vulnerability spreads.

References

github.com/hackmdio/codimd/issues/1846 (opens in a new tab)

Community reviews

Loading reviews…