CVE-2024-10497
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 · uneditedCWE-639: Authorization Bypass Through User-Controlled Key vulnerability exists that could allow an authorized attacker to modify values outside those defined by their privileges (Elevation of Privileges) when the attacker sends modified HTTPS requests to the device.
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 confidenceCWE-639 (Authorization Bypass Through User-Controlled Key) vulnerability allows an authenticated attacker to manipulate key values in HTTPS requests to access or modify data outside their authorized scope, resulting in elevation of privileges on the affected device.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed software versionLocate the software's version information through its admin interface, command-line tool, or system files (check documentation for version location)Affected if The installed version falls within any vulnerable version range for this CVE, if known
-
Confirm authenticated access is possibleVerify that user accounts can be created and authenticated on the system, as this vulnerability requires an authenticated attackerAffected if The system accepts and processes authenticated user sessions
-
Identify endpoints accepting user-controllable key parametersReview API documentation or intercept HTTPS requests to find parameters that accept IDs, references, or keys that a user might control (such as object IDs, record IDs, or resource identifiers)Affected if The application exposes endpoints where users can submit key values in requests
-
Verify authorization validation on key parametersTest whether the application properly validates that the authenticated user has permission to access or modify the specific resource identified by the user-controllable key, regardless of the key value submittedAffected if The application does not validate user permissions based on the user-controllable key, allowing unauthorized access to resources outside the user's scope
-
Check for privilege escalation behaviorAttempt to access or modify resources belonging to other users or higher-privilege accounts by manipulating key values while authenticated as a lower-privilege userAffected if An authenticated user can access or modify data outside their authorized scope by manipulating key values
A user is affected if they are running a version within the vulnerable range and the application permits authenticated users to manipulate key parameters to access resources beyond their authorized permissions.
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.
From vendor dataImplement proper server-side authorization validation ensuring all resource access requests are validated against the authenticated user's permissions, regardless of any user-controllable key parameters in the request.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10497 — 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-10497 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