dbcve.org
CodecheckerApplication · Ericsson

CVE-2024-10082

CRITICAL · 9.0 CVSS v3.1 Published 2024-11-06
Fix available
A fix is available. Upgrade to 6.24.2 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy. Authentication method confusion allows logging in as the built-in root user from an external service. The built-in root user up until 6.24.1 is generated in a weak manner, cannot be disabled, and has universal access.This vulnerability allows an attacker who can create an account on an enabled external authentication service, to log in as the root user, and access and control everything that can be controlled via the web interface. The attacker needs to acquire the username of the root user to be successful. This issue affects CodeChecker: through 6.24.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CodeChecker suffers from an authentication method confusion vulnerability where the built-in root user (generated with weak credentials through version 6.24.1) can be authenticated via an external authentication service. An attacker with an account on an enabled external identity provider who obtains the root username can impersonate the root user and gain full web interface access.

MitigationUpgrade to a version beyond 6.24.1 which should address the weak root user generation and/or disable the built-in root user. Until patched, disable external authentication if possible and strictly control access to external identity providers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CodecheckerApplication
Affected:< 6.24.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify CodeChecker version
    Run 'CodeChecker --version' or check the package/version metadata in your installation directory
    Affected if The installed version is lower than 6.24.2
  2. Determine if root user was created
    Check for the presence of a root account in the CodeChecker user database or configuration files (e.g., ~/.codechecker/projects.yaml or the configured authentication backend)
    Affected if A built-in root user account exists in the system
  3. Check if external authentication is enabled
    Review CodeChecker configuration files (typically in the service config) for external authentication providers such as LDAP, OAuth, or OIDC configuration sections
    Affected if External authentication providers are configured and enabled in CodeChecker
  4. Verify root username exposure
    Review access logs, configuration comments, or documentation that may reveal the default root username used during CodeChecker setup
    Affected if The root username is known or discoverable in the environment

You are affected if you run CodeChecker version below 6.24.2 AND have both the built-in root user enabled AND external authentication configured, allowing an attacker with external identity provider access to impersonate root.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.24.2 or later
Fixed in 6.24.2
Interim mitigation

Upgrade to a version beyond 6.24.1 which should address the weak root user generation and/or disable the built-in root user. Until patched, disable external authentication if possible and strictly control access to external identity providers.

Recommended fix High confidence

CodeChecker 6.24.2

  1. Review CodeChecker 6.24.2 release notes for any breaking changes or migration requirements
  2. Backup your existing CodeChecker configuration, database, and any custom settings
  3. Upgrade CodeChecker to version 6.24.2 or later using your package manager or build system
  4. Verify the upgrade was successful by checking the installed version
  5. Restart CodeChecker services if applicable
  6. Test that authentication functions correctly after the upgrade
Caveat Review release notes for potential breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Codechecker Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10082 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data