CVE-2024-33872
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 10.5.x before 10.5.1 and 11.5.x before 11.5.1 allows SQL Injection which could result in code execution and escalation of privileges.
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 confidenceSQL injection vulnerability in Keyfactor Command versions 10.5.x before 10.5.1 and 11.5.x before 11.5.1 allows attackers to inject malicious SQL queries, potentially achieving code execution on the underlying database server and escalating privileges within the application.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Keyfactor Command versionCheck the Keyfactor Command web interface version banner (typically in the footer of the application), or query the service/API endpoint for version information, or inspect the installation directory for version manifest filesAffected if The version displayed is 10.5.x or 11.5.x and is below 10.5.1 or 11.5.1 respectively
-
Compare version against affected rangesReview the identified version number against the known affected ranges: 10.5.x (any version before 10.5.1) and 11.5.x (any version before 11.5.1)Affected if The installed version is 10.5.0 through 10.5.0.x, or 11.5.0 through 11.5.0.x, placing it before the patched releases
-
Confirm Keyfactor Command productVerify that the application being checked is indeed Keyfactor Command and not another Keyfactor product, by reviewing the product name in the administration interface or license informationAffected if The product is Keyfactor Command and the version falls within the affected ranges
If the installed Keyfactor Command version is 10.5.x before 10.5.1 or 11.5.x before 11.5.1, the environment is affected by this SQL injection vulnerability.
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 10.5.1 or 11.5.1 or later to obtain the patched code that properly sanitizes SQL inputs.
Keyfactor Command 10.5.1 or later for 10.5.x line; Keyfactor Command 11.5.1 or later for 11.5.x line
- Identify the currently installed Keyfactor Command version by checking the application or system information
- If running Keyfactor Command 10.5.x, upgrade to version 10.5.1 or later
- If running Keyfactor Command 11.5.x, upgrade to version 11.5.1 or later
- After upgrading, verify the SQL injection vulnerability is remediated by confirming the fix is applied
- Test that core certificate management functionality continues to work as expected post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33872 — 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-33872 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