CVE-2024-0580
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 · uneditedOmission of user-controlled key authorization in the IDMSistemas platform, affecting the QSige product. This vulnerability allows an attacker to extract sensitive information from the API by making a request to the parameter '/qsige.locator/quotePrevious/centers/X', where X supports values 1,2,3, etc.
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in the IDMSistemas QSige product. The API endpoint '/qsige.locator/quotePrevious/centers/X' lacks proper authorization controls, allowing unauthenticated attackers to access sensitive center data by manipulating the numeric parameter (1, 2, 3, etc.). This enables unauthorized extraction of potentially sensitive information from the API.
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= 2.0CVSS 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 installed productLocate Idmsistemas Sinergia or QSige in your environment by checking installed software, running services, or application directoriesAffected if Idmsistemas Sinergia version 2.0 is installed
-
Verify product versionCheck the installed version of Idmsistemas Sinergia against version 2.0 using product-specific commands, configuration files, or the application itselfAffected if Version equals 2.0
-
Confirm endpoint exposureAttempt an HTTP request to the path /qsige.locator/quotePrevious/centers/ on your server or check web server logs for access attemptsAffected if The endpoint is accessible and responds to requests
-
Test unauthenticated accessSend a request to the endpoint without any authentication headers or session cookies and observe whether data is returnedAffected if The endpoint returns data without requiring authentication
-
Verify IDOR via parameter manipulationSend requests with different numeric values in the URL such as /centers/1, /centers/2, /centers/3 and compare whether different center records are returnedAffected if Different center data is returned for different numeric parameters without authorization checks
If Sinergia version is 2.0 and the /qsige.locator/quotePrevious/centers/X endpoint returns data without authentication or authorization, the environment is affected by CVE-2024-0580.
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 authorization checks to verify the requesting user has permission to access the specific center data. Replace direct object references with indirect references and enforce authentication requirements on the affected endpoint.
- 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-0580 — 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-0580 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