CVE-2019-3683
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 keystone-json-assignment package in SUSE Openstack Cloud 8 before commit d7888c75505465490250c00cc0ef4bb1af662f9f every user listed in the /etc/keystone/user-project-map.json was assigned full "member" role access to every project. This allowed these users to access, modify, create and delete arbitrary resources, contrary to expectations.
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 keystone-json-assignment package in SUSE OpenStack Cloud 8 had a broken access control flaw where every user listed in /etc/keystone/user-project-map.json was automatically granted full 'member' role access to ALL projects, rather than being restricted to only their intended projects. This allowed unauthorized users to access, modify, create, and delete resources across the entire cloud environment.
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= 8.0< 2019-02-18= 8.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify keystone-json-assignment installationRun: rpm -qa | grep keystone-json-assignment or dpkg -l | grep keystone-json-assignmentAffected if The package is installed and its version is earlier than 2019-02-18
-
Locate user-project-map.jsonInspect the file /etc/keystone/user-project-map.json for existence and contentAffected if The file exists and contains user-to-project mappings
-
Verify role assignment behaviorUse OpenStack CLI: openstack role assignment list --names to list all role assignments; check if users from user-project-map.json have 'member' role on projects they should NOT have access toAffected if Users listed in user-project-map.json are granted member role on projects outside their intended mapping
-
Audit cross-project accessFor each user in user-project-map.json, run: openstack role assignment list --user <username> --names to identify all projects where they hold the member roleAffected if A user has member access to more projects than what their entry in user-project-map.json specifies
If keystone-json-assignment version is less than 2019-02-18 AND the user-project-map.json file exists with user entries, then users are likely granted excessive member role permissions across all projects.
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 data2019-02-18
Apply the fix from commit d7888c75505465490250c00cc0ef4bb1af662f9f to the keystone-json-assignment package, then audit and correct the user-project-map.json configuration to ensure only intended users have access to intended projects, and remove any unauthorized role assignments.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3683 — 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-2019-3683 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