CVE-2024-49202
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 · uneditedKeyfactor Command before 12.5.0 has Incorrect Access Control: access tokens are over permissioned, aka 64099. The fixed versions are 11.5.1.1, 11.5.2.1, 11.5.3.1, 11.5.4.5, 11.5.6.1, 11.6.0, 12.2.0.1, 12.3.0.1, 12.4.0.1, 12.5.0, and 24.4.0.
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 · moderate confidenceKeyfactor Command before 12.5.0 contains an Incorrect Access Control vulnerability where access tokens are granted more permissions than intended by the authorization model, allowing authenticated users to perform actions beyond their authorized privilege level.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Keyfactor Command versionCheck the installed Keyfactor Command version via the administration UI (Help > About) or by inspecting the web.config or appsettings.json file in the installation directoryAffected if The version is earlier than 12.5.0, or earlier than 11.5.1.1 for 11.x releases, earlier than 12.2.0.1 for 12.x releases, or earlier than 24.4.0 for 24.x releases
-
Verify access control configurationReview the role-based access control (RBAC) settings in Keyfactor Command under Administration > Roles and Users to confirm the permission modelAffected if Authenticated users with limited roles can access functionality or data outside their assigned role permissions
-
Audit token-based accessExamine access tokens issued by Keyfactor Command using the API or audit logs to check if token scopes match the assigned role permissionsAffected if Tokens contain permissions or capabilities that exceed what the user's assigned role should allow
A user is affected if their Keyfactor Command installation version is before 12.5.0 (or before the relevant patched version for their release branch) AND they have authenticated users whose access tokens may exceed their intended privilege level.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Keyfactor Command to version 12.5.0 or later, or apply the appropriate patched version for your release branch (11.5.1.1, 11.5.2.1, 11.5.3.1, 11.5.4.5, 11.5.6.1, 11.6.0, 12.2.0.1, 12.3.0.1, 12.4.0.1, or 24.4.0).
Upgrade to Keyfactor Command 12.5.0 or 24.4.0 (latest stable releases)
- Identify the current Keyfactor Command version installed in your environment
- Determine the appropriate upgrade path based on your current version to reach one of the fixed releases
- Review Keyfactor upgrade documentation for your specific version transition
- Schedule a maintenance window for the upgrade process
- Backup the current Keyfactor Command database and configuration
- Perform the upgrade to version 12.5.0, 24.4.0, or another listed fixed version (11.5.1.1, 11.5.2.1, 11.5.3.1, 11.5.4.5, 11.5.6.1, 11.6.0, 12.2.0.1, 12.3.0.1, or 12.4.0.1)
- Verify the upgrade completed successfully
- Test that access tokens now have correct, non-overpermissioned access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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