CVE-2016-2100
foreman: Unprivileged user can access private bookmarks of other users
Overview
Description
Foreman 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.
Source: OX vulnerability database
Severity
5.4 · MEDIUM
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- 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
Weakness: CWE-284
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 162 fixes
Red Hat 1 release · 162 packages
fixed 162
libstemmer
tfm-rubygem-apipie-bindings
tfm-rubygem-fog-libvirt
tfm-rubygem-rbovirt
tfm-rubygem-apipie-params
tfm-rubygem-fog-google
+156
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 7 | libstemmer | 0:0-2.585svn.el7sat | RHBA-2016:1500 |
| 7 | tfm-rubygem-apipie-bindings | 0:0.0.16-1.el7sat | RHBA-2016:1500 |
| 7 | tfm-rubygem-fog-libvirt | 0:0.0.2-3.el7sat | RHBA-2016:1500 |
| 7 | tfm-rubygem-rbovirt | 0:0.0.37-1.el7sat | RHBA-2016:1500 |
| 7 | tfm-rubygem-apipie-params | 0:0.0.5-2.el7sat | RHBA-2016:1500 |
| 7 | tfm-rubygem-fog-google | 0:0.1.0-2.el7sat | RHBA-2016:1500 |
156 more rows
References
- projects.theforeman.org http://projects.theforeman.org/issues/13828
- theforeman.org http://theforeman.org/security.html#2016-2100
- www.openwall.com http://www.openwall.com/lists/oss-security/2016/03/31/2
- access.redhat.com https://access.redhat.com/errata/RHBA-2016:1500
- access.redhat.com https://access.redhat.com/security/cve/CVE-2016-2100
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2016-2100
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2016-2100
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.