CVE-2024-29843
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 MOBILE_GET_USERS_LIST, allowing for an unauthenticated attacker to enumerate all users and their access levels
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 versions 2.04.560.31.03.2024 and below has a broken access control vulnerability on the MOBILE_GET_USERS_LIST endpoint. This endpoint exposes user information and access levels to unauthenticated attackers, allowing full user enumeration without any credentials.
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 if Evolution Controller web interface is runningCheck your environment for running web services on common ports (typically 80/443) or look for the Evolution Controller application. Inspect network connections or check installed services to confirm the product is present.Affected if The Evolution Controller web interface is installed and accessible on your network.
-
Determine the installed Evolution versionAccess the web interface help, about page, or login screen and locate the version information. If available, check the administrative panel or system information section for the exact build version (e.g., 2.04.560 or lower).Affected if The installed version is 2.04.560 or any version dated on or before 31.03.2024.
-
Verify the MOBILE_GET_USERS_LIST endpoint existsSend an HTTP GET request to your Evolution Controller host targeting the path /mobile/MOBILE_GET_USERS_LIST or similar endpoint structure. Inspect the response to confirm the endpoint is present and responds to requests.Affected if The MOBILE_GET_USERS_LIST endpoint is accessible and returns a valid HTTP response.
-
Confirm the endpoint is accessible without authenticationSend a request to the MOBILE_GET_USERS_LIST endpoint without providing any authentication credentials (no session cookie, no Authorization header, no login token). Verify the request succeeds without being redirected to a login page or receiving a 401/403 error.Affected if The endpoint returns user data (usernames, access levels, or similar) without requiring any login credentials.
You are affected if Evolution Controller version 2.04.560 or lower is running and the MOBILE_GET_USERS_LIST endpoint returns user information without authentication.
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 authorization checks on the MOBILE_GET_USERS_LIST endpoint to ensure only authenticated users with appropriate privileges can access user information. Consider conducting a broader access control audit to identify similar vulnerabilities.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29843 — 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-29843 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