CVE-2024-40060VulnerabilityPublished 23 Jul 2024Updated 16 Aug 2024

CVE-2024-40060: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 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 50% 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 23 Jul 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

AI-suggested

To mitigate CVE-2024-40060, organizations should first monitor the go-chart project for official patches or updates addressing the infinite loop issue and apply them promptly once available. In the interim, developers can review and modify the drawCanvas() function to add loop exit conditions or timeouts to prevent infinite execution. Implementing resource limits such as CPU usage caps or container-level constraints can reduce the impact of potential infinite loops. Additionally, deploying web application firewalls (WAFs) or network-level rate limiting can help detect and block abnormal requests targeting the vulnerable function. Conduct thorough code audits for similar looping constructs in custom integrations. Finally, consider isolating services using go-chart to minimize the blast radius of a potential DoS attack and maintain robust monitoring to detect unusual resource consumption patterns early.

Description

go-chart v2.1.1 was discovered to contain an infinite loop via the drawCanvas() function.

Impact

The primary impact of CVE-2024-40060 is a denial-of-service condition caused by an infinite loop in the drawCanvas() function. This can lead to resource exhaustion on affected systems, resulting in application crashes, degraded performance, or complete service outages. Since the vulnerability can be triggered remotely without authentication or user interaction, attackers can easily disrupt services, affecting availability. While confidentiality and integrity remain intact, the availability impact can cause significant operational disruptions, especially for services relying on real-time or high-availability chart rendering. This may affect web applications, dashboards, monitoring tools, and any automated reporting systems using go-chart. The lack of patches increases the window of exposure, and organizations may face increased risk of downtime or service interruptions until mitigations are applied.

References

gist.github.com/F3iG0n9/4d0d7c863eea6874eeeb26a3073aa5f8 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 05:11 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats