CVE-2016-2100
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 · uneditedForeman before 1.10.3 and 1.11.0 before 1.11.0-RC2 allow remote authenticated users to read, modify, or delete private bookmarks by leveraging the (1) edit_bookmarks or (2) destroy_bookmarks permission.
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 · moderate confidenceForeman versions before 1.10.3 and 1.11.0 before 1.11.0-RC2 contain an insecure direct object reference (IDOR) vulnerability in the bookmark functionality. Authenticated users with edit_bookmarks or destroy_bookmarks permissions can read, modify, or delete private bookmarks belonging to other users due to insufficient authorization checks on bookmark 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<= 1.10.2= 1.11.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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Determine installed Foreman versionLocate the Foreman version file or use the foreman-admin command (foreman --version or hammer ping) to retrieve the running version. Compare this version number against the affected ranges: any version <= 1.10.2 or exactly version 1.11.0 is vulnerable.Affected if The installed Foreman version is 1.10.2 or earlier, or exactly 1.11.0.
-
Identify bookmark-related role permissionsAccess the Foreman admin UI under Administer > Users > [select user] > Roles tab, or use the API endpoint /api/v2/users to enumerate user role assignments. Look specifically for roles that include the edit_bookmarks or destroy_bookmarks permissions.Affected if Any authenticated user account has been assigned a role containing edit_bookmarks or destroy_bookmarks permissions.
-
Verify private bookmarks exist in the systemQuery the bookmarks table via Foreman database (select * from bookmarks where is_public = false) or navigate to Hosts > Bookmarks in the UI to list existing bookmark entries. Private bookmarks are those with the is_public flag set to false.Affected if There are private (non-public) bookmarks created by users in the system.
-
Check for unauthorized bookmark access capabilityUsing a test user account that has edit_bookmarks or destroy_bookmarks permissions but is NOT the owner of a private bookmark, attempt to view, modify, or delete that bookmark via the API (GET/PUT/DELETE /api/bookmarks/:id) or UI. Success indicates the IDOR vulnerability is present.Affected if A user with bookmark edit/destroy permissions can access, modify, or delete bookmarks they do not own.
If Foreman version is <=1.10.2 or exactly 1.11.0 AND bookmark permissions are assigned to users who should not have access to other users private bookmarks, the environment is affected by this IDOR vulnerability.
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 Foreman to version 1.10.3, 1.11.0-RC2, or later. As an interim measure, audit user role assignments and restrict bookmark-related permissions to only trusted users until the upgrade can be completed.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2100 — 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-2100 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