CVE-2024-57716
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 · uneditedAn issue in trenoncourt AutoQueryable v.1.7.0 allows a remote attacker to obtain sensitive information via the Unselectable function.
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 confidenceAutoQueryable v1.7.0 contains an information disclosure vulnerability in the Unselectable function that allows unauthenticated remote attackers to access sensitive data they should not be able to retrieve. The Unselectable function appears to have insufficient access controls or logic flaws that permit enumeration or exposure of restricted information.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 AutoQueryable installationCheck your project dependencies (NuGet packages, package.json, requirements.txt, or similar) to locate the AutoQueryable libraryAffected if AutoQueryable is present in dependencies but version cannot be verified or is 1.7.0
-
Verify the installed versionQuery your package manager or dependency lock file for the exact version of AutoQueryable (e.g., dotnet list package, NuGet package manager, or check packages.config)Affected if The installed version is 1.7.0 or the version cannot be determined from available metadata
-
Determine if Unselectable function is exposedReview your API endpoints, OData configuration, or AutoQueryable setup code to see if the Unselectable function is enabled or accessibleAffected if The Unselectable function is exposed via API endpoint or OData controller without authentication requirements
-
Check authentication status on endpoints using AutoQueryableInspect the controller or endpoint configuration that uses AutoQueryable to verify if authentication is required for all operations including UnselectableAffected if Endpoints utilizing the Unselectable function allow unauthenticated access or lack explicit authorization checks
You are affected if AutoQueryable version 1.7.0 is installed and the Unselectable function is exposed without authentication or authorization controls.
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 dataIf a patched version is available, upgrade immediately. Otherwise, review and restrict access to the Unselectable function, implement proper authorization checks, or disable the function until a fix is available.
- 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-57716 — 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-57716 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