CVE-2024-53829: Cross-Site Request Forgery in CodeChecker API
Summary 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 <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.
Other sources
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 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.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53829?
CVE-2024-53829 is considered a high severity vulnerability due to its potential for cross-site request forgery attacks.
How does CVE-2024-53829 affect users?
CVE-2024-53829 allows an unauthenticated attacker to hijack the authentication of a logged-in user, compromising their account.
How do I fix CVE-2024-53829?
To mitigate CVE-2024-53829, update the CodeChecker to version 6.24.5 or later.
What are the main issues with CVE-2024-53829?
The main issues with CVE-2024-53829 include missing security attributes like HttpOnly and SameSite on the session cookie.
Who is affected by CVE-2024-53829?
Users of CodeChecker prior to version 6.24.5 are affected by CVE-2024-53829.