GHSA-F8C8-4PM7-W885
Vulnerability from github – Published: 2025-01-21 20:25 – Updated: 2025-04-08 17:52Summary
Cross-site request forgery allows an unauthenticated attacker to hijack the authentication of a logged in user, and use the web API with the same permissions.
Details
Security attributes like HttpOnly and SameSite are missing from the session cookie, allowing its use from XHR requests and form submissions. The CodeChecker API endpoints only require the session cookie, they do not require a CSRF token, and missing HTTP headers allow the form submission to succeed (but not XHR). This means that the attacker needs to know the ID of products to edit or delete them, but it does not need knowledge to create new products with the SQLite backend.
PoC
With a superuser logged into CodeChecker.
<html><body>
<form action="https://codechecker.example.com/v6.58/Products" method="POST" enctype="text/plain">
<input type="text" name='[1,"getProducts",1,1,{}]' value=''>
</form>
<script>document.forms[0].submit()</script>
</body></html>
Or the same form attack on any of the applicable endpoints.
Impact
The vulnerability allows an attacker to make requests to CodeChecker as the currently logged in user, 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 from CodeChecker, due to being limited to form-based CSRF.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "codechecker"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.24.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-53829"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": true,
"github_reviewed_at": "2025-01-21T20:25:05Z",
"nvd_published_at": "2025-01-21T15:15:13Z",
"severity": "HIGH"
},
"details": "### Summary\nCross-site request forgery allows an unauthenticated attacker to hijack the authentication of a logged in user, and use the web API with the same permissions.\n\n### Details\nSecurity attributes like HttpOnly and SameSite are missing from the session cookie, allowing its use from XHR requests and form submissions.\nThe CodeChecker API endpoints only require the session cookie, they do not require a CSRF token, and missing HTTP headers allow the form submission to succeed (but not XHR). This means that the attacker needs to know the ID of products to edit or delete them, but it does not need knowledge to create new products with the SQLite backend.\n\n### PoC\nWith a superuser logged into CodeChecker.\n\n```html\n\u003chtml\u003e\u003cbody\u003e\n \u003cform action=\"https://codechecker.example.com/v6.58/Products\" method=\"POST\" enctype=\"text/plain\"\u003e\n \u003cinput type=\"text\" name=\u0027[1,\"getProducts\",1,1,{}]\u0027 value=\u0027\u0027\u003e\n \u003c/form\u003e\n \u003cscript\u003edocument.forms[0].submit()\u003c/script\u003e\n\u003c/body\u003e\u003c/html\u003e\n```\nOr the same form attack on any of the applicable endpoints.\n\n### Impact\nThe vulnerability allows an attacker to make requests to CodeChecker as the currently logged in user, 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 from CodeChecker, due to being limited to form-based CSRF.",
"id": "GHSA-f8c8-4pm7-w885",
"modified": "2025-04-08T17:52:35Z",
"published": "2025-01-21T20:25:05Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Ericsson/codechecker/security/advisories/GHSA-f8c8-4pm7-w885"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53829"
},
{
"type": "PACKAGE",
"url": "https://github.com/Ericsson/codechecker"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/codechecker/PYSEC-2025-12.yaml"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Cross-Site Request Forgery in CodeChecker API"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.