Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2018-1101

ansible-tower: Privilege escalation flaw allows for organization admins to obtain system privileges

Overview

Published
2 May 2018
Modified
17 Jun 2026
High CVE
0 Registry packages
32 OS packages
1 Linux distributions
Yes Fix available

Description

Ansible Tower before version 3.2.4 has a flaw in the management of system and organization administrators that allows for privilege escalation. System administrators that are members of organizations can have their passwords reset by organization administrators, allowing organization administrators access to the entire system.

Source: OX vulnerability database

Severity

7.2 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-266, CWE-521

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 14 fixes

Red Hat 1 release · 10 packages

fixed 14
httpd-configmap-generator rh-ruby23-rubygem-qpid-proton dbus-api-service rh-ruby23-rubygem-json python-paramiko ansible +4
Red Hat fixes for CVE-2018-1101
ReleasePackageFixed inAdvisory
7 httpd-configmap-generator 0:0.2.1-2.el7cf RHSA-2018:1328
7 rh-ruby23-rubygem-qpid-proton +1 0:0.22.0-2.el7cf RHSA-2018:1328
7 dbus-api-service 0:1.0.1-3.el7cf RHSA-2018:1328
7 rh-ruby23-rubygem-json +1 0:2.1.0-1.el7cf RHSA-2018:1328
7 rh-ruby23-rubygem-json +1 0:2.1.0-1.el7cf RHSA-2018:1972
7 python-paramiko +1 0:2.1.1-4.el7 RHSA-2018:1328

8 more rows

References

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.