CloudstackApplication · Apache
CVE-2016-6813
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 · uneditedApache CloudStack 4.1 to 4.8.1.0 and 4.9.0.0 contain an API call designed to allow a user to register for the developer API. If a malicious user is able to determine the ID of another (non-"root") CloudStack user, the malicious user may be able to reset the API keys for the other user, in turn accessing their account and resources.
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 confidenceApache CloudStack contains an insecure API endpoint for developer API registration that lacks proper authorization checks. A malicious user who can enumerate another non-root user's ID can call this API to reset that user's API keys, effectively achieving account takeover and gaining access to the victim's resources.
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
CloudstackApplication
>= 4.1.0, <= 4.8.1.0= 4.9.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check Apache CloudStack installed versionRun 'cloudmonkey' or access the management server UI, or check the RPM/DEB package version with 'rpm -q cloudstack-management' or 'dpkg -l | grep cloudstack'Affected if The installed version is 4.1.0 through 4.8.1.0, or exactly 4.9.0
-
Identify if developer API registration endpoint is enabledReview CloudStack configuration files (typically in /etc/cloudstack/management or the management server properties) for any developer or regusterAPIkey settings; also check if the 'registerUserApiKey' or similar developer API endpoint is accessible on port 8096 or the management portAffected if The developer API registration endpoint is exposed and not disabled via configuration
-
Test API key reset capability for other usersUsing an authenticated low-privilege user account, attempt to call the API with a known user ID that is not your own (e.g., via cloudmonkey: 'resetUserApiKey userid=<different_user_id>')Affected if The API call succeeds and returns a new API key for a different user without requiring admin privileges
-
Verify user ID enumeration is possibleAttempt to enumerate valid user IDs by observing API responses when querying user-related commands or checking if error messages reveal whether specific user IDs existAffected if Non-admin users can discover other valid user IDs in the system through API responses
A user is affected if running a vulnerable CloudStack version (4.1.0-4.8.1.0 or 4.9.0) where the developer API registration endpoint is exposed and allows a non-admin user to reset API keys for other users by exploiting user ID enumeration.
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 dataUpgrade to a patched version of Apache CloudStack. Additionally, implement API request rate limiting and monitoring to detect user ID enumeration attempts.
Fix this in Cloudstack
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6813 — 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-2016-6813 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