OpenstackApplication · Redhat
CVE-2013-2113
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 create method in app/controllers/users_controller.rb in Foreman before 1.2.0-RC2 allows remote authenticated users with permissions to create or edit other users to gain privileges by (1) changing the admin flag or (2) assigning an arbitrary role.
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 create method in Foreman's users_controller.rb allows authenticated users with permissions to create or edit other users to escalate privileges by either changing the admin flag or assigning arbitrary roles, bypassing intended authorization controls.
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
OpenstackApplication
= 3.0<= 1.2.0= 1.1CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
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 installed Foreman versionRun `rpm -qa | grep foreman` or check the UI at Administer > About Foreman to find the exact version numberAffected if Version is 1.1 or any version <= 1.2.0 (including 1.2.0)
-
Verify the vulnerable users_controller.rb code existsLocate the users_controller.rb file (typically in app/controllers/users_controller.rb) and examine the create method for missing authorization checks on the admin flag and role assignmentAffected if The create method lacks proper authorization checks before setting admin=true or assigning roles
-
Identify users with user management permissionsReview which users have the edit_users or create_users permission by checking the Roles configuration in Foreman at Administer > RolesAffected if Any authenticated user account has permissions to create or edit users (not limited to admin-only)
-
Review user accounts for unauthorized admin flagsQuery the users table or check via the UI at Hosts > Users to identify any user accounts that have admin=true but should not have administrative privilegesAffected if There exist user accounts with admin=true that were created by non-admin users or that should not have admin privileges
You are affected if Foreman version is 1.1 or <= 1.2.0 and any authenticated user with user creation/edit permissions can escalate privileges via the admin flag or arbitrary role assignment.
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 Foreman version 1.2.0-RC2 or later which contains proper authorization checks for the user creation and role assignment functionality.
Fix this in Openstack
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2113 — 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-2013-2113 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