Cyber Resilience

CVE-2024-53829

CSRF in Ericsson Codechecker ≤ 6.24.5

Public PoCCSRF
Published
21 January 2025
Modified
14 November 2025
Patch / advisory
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N
EPSS Score 0.0025 16th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2024-53829 is a high-severity CSRF (CWE-352) vulnerability in Ericsson Codechecker. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-53829 is a cross-site request forgery (CSRF) vulnerability, classified under CWE-352, in CodeChecker, an analyzer tooling, defect database, and viewer extension for the Clang Static Analyzer and Clang Tidy. The flaw allows an unauthenticated attacker to hijack the authentication of a logged-in user and perform actions via the web API with the victim's permissions. It affects CodeChecker versions through 6.24.4 and carries a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N).

An unauthenticated attacker can exploit this vulnerability by tricking a logged-in user into interacting with a malicious webpage or resource that submits forged requests to the CodeChecker web API. Successful exploitation grants the attacker the same permissions as the victim, enabling actions such as adding, removing, or editing products. However, the attacker must know the IDs of existing products to modify or delete them and cannot directly exfiltrate data (e.g., view reports) due to the form-based nature of the CSRF limitation.

The GitHub security advisory at https://github.com/Ericsson/codechecker/security/advisories/GHSA-f8c8-4pm7-w885 provides details on the issue, including mitigation guidance. Affected users should upgrade to CodeChecker versions beyond 6.24.4, where the vulnerability is addressed.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy. Cross-site request forgery allows an unauthenticated attacker to hijack the authentication of a logged in user, and use the web API with…

more

the same permissions, including but not limited to adding, removing or editing products. The attacker needs to know the ID of the available products to modify or delete them. The attacker cannot directly exfiltrate data (view) from CodeChecker, due to being limited to form-based CSRF. This issue affects CodeChecker: through 6.24.4.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-8489Shared CWE-352
CVE-2024-51638Shared CWE-352
CVE-2025-23804Shared CWE-352
CVE-2024-36667Shared CWE-352
CVE-2024-26445Shared CWE-352
CVE-2024-22601Shared CWE-352
CVE-2023-50766Shared CWE-352
CVE-2025-9635Shared CWE-352
CVE-2025-30541Shared CWE-352
CVE-2023-27520Shared CWE-352

Affected Assets

ericsson
codechecker
≤ 6.24.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References