CVE-2024-29841
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_KEYS_FIELDS, allowing for an unauthenticated attacker to return the keys value 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 confidenceThe Evolution Controller web interface contains a poorly configured access control on the DESKTOP_EDIT_USER_GET_KEYS_FIELDS endpoint. This allows unauthenticated attackers to retrieve the keys/credentials of any user in the system by directly accessing this endpoint without authentication, exposing sensitive cryptographic material.
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 versionLocate the installed Cs Technologies Evolution application and check its version number. This is typically visible in the application UI, an about dialog, or in installation/log files. Compare against the affected range: any version <= 2.04.560 is vulnerable.Affected if Installed version is 2.04.560 or lower
-
Confirm web interface is accessibleVerify that the Evolution web interface is running and network-accessible. Attempt to reach the base URL of the web application in a browser or via curl/wget to confirm it responds.Affected if Web interface is exposed and responds to requests
-
Test vulnerable endpoint without authenticationSend an HTTP GET request to the DESKTOP_EDIT_USER_GET_KEYS_FIELDS endpoint without providing any authentication credentials. For example: curl -v http://[target]/[path-to-evolution]/DESKTOP_EDIT_USER_GET_KEYS_FIELDSAffected if The endpoint returns HTTP 200 OK or any successful response without requiring login
-
Verify sensitive data exposureExamine the response from the unauthenticated endpoint. Check if it contains cryptographic keys, credentials, or sensitive user data in the returned JSON or response body.Affected if The unauthenticated response contains keys, credentials, or sensitive user information
A user is affected if the Evolution web interface is running version 2.04.560 or lower AND the DESKTOP_EDIT_USER_GET_KEYS_FIELDS endpoint is accessible without authentication and returns sensitive credential data.
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 role-based authorization checks on the DESKTOP_EDIT_USER_GET_KEYS_FIELDS endpoint to ensure only authenticated administrators can access user key data. If a patch is available from the vendor, apply it.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29841 — 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-29841 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