CVE-2024-29839
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 · uneditedThe Web interface of Evolution Controller Versions 2.04.560.31.03.2024 and below contains poorly configured access control on DESKTOP_EDIT_USER_GET_CARD, allowing for an unauthenticated attacker to return the card value data of any user
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 confidenceEvolution Controller Web interface versions 2.04.560.31.03.2024 and below has a broken access control vulnerability on the DESKTOP_EDIT_USER_GET_CARD endpoint. This endpoint lacks proper authentication and authorization checks, allowing any unauthenticated attacker to query and retrieve sensitive card value data belonging to any user in the system.
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.04.560CVSS 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 Evolution Controller versionCheck the web interface version by accessing the login page or system information page, or query the application's API endpoints for version informationAffected if The installed version is 2.04.560 or lower (e.g., 2.04.560.31.03.2024)
-
Verify the DESKTOP_EDIT_USER_GET_CARD endpoint existsMake an HTTP GET or POST request to the DESKTOP_EDIT_USER_GET_CARD endpoint (typically under the application's API path) without providing any authentication credentialsAffected if The endpoint responds with HTTP 200 or any data without requiring a login session or token
-
Test unauthenticated access to user card dataSend a request to the endpoint with a valid user identifier (such as a user ID or username) in the request parameters without being logged inAffected if The response contains sensitive card value data belonging to any user in the system without authentication
-
Confirm lack of session validationInspect HTTP response headers and cookies to verify no authentication session or authorization token is being validated by the endpointAffected if The endpoint returns valid data without checking for a valid authenticated session
-
Check if web interface is internet-facingReview network configuration or firewall rules to determine if the Evolution Controller web interface is accessible from external networksAffected if The web interface is exposed externally and the version is within the affected range
A user is affected if running Evolution Controller version 2.04.560 or lower AND the DESKTOP_EDIT_USER_GET_CARD endpoint returns sensitive card data without requiring authentication credentials.
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 authentication and session validation on the DESKTOP_EDIT_USER_GET_CARD endpoint, and add role-based authorization checks to ensure users can only access their own card data. Conduct a broader security audit to identify similar access control flaws across the application.
- 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-29839 — 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-29839 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