CVE-2022-38060
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 · uneditedA privilege escalation vulnerability exists in the sudo functionality of OpenStack Kolla git master 05194e7618. A misconfiguration in /etc/sudoers within a container can lead to increased privileges.
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 confidenceOpenStack Kolla containers contain a misconfigured /etc/sudoers file that permits privilege escalation. An attacker with container access can exploit the sudo misconfiguration to gain elevated root privileges on the host system.
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 dataall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 Kolla containers in useRun 'docker ps' or 'podman ps' to list running containers, or check Kolla deployment manifests and inventory files to identify containers managed by OpenStack KollaAffected if Kolla containers are present in the environment
-
Locate /etc/sudoers in Kolla containersAccess a Kolla container shell (e.g., 'docker exec -it <container_name> /bin/bash') and locate the file at /etc/sudoers, or extract it directly using 'docker cp <container_name>:/etc/sudoers /tmp/'Affected if The /etc/sudoers file exists inside Kolla containers
-
Inspect sudoers file for misconfigurationView the contents of /etc/sudoers inside the container using 'cat /etc/sudoers' or 'visudo -c' to validate syntax. Look for entries that allow privilege escalation such as 'ALL=(ALL) NOPASSWD: ALL' or overly permissive user/group rulesAffected if The sudoers file contains rules permitting passwordless root access or unrestricted sudo privileges for non-root users
-
Verify container-to-host privilege escalation pathFrom within the container, test if a non-root user can execute sudo commands without authentication (e.g., 'sudo whoami' returns 'root')Affected if Sudo commands execute successfully without requiring a password, confirming the misconfiguration allows host privilege escalation
If the /etc/sudoers file in any Kolla container contains overly permissive sudo rules (such as NOPASSWD: ALL), the environment is vulnerable to CVE-2022-38060 and an attacker with container access can escalate to host root privileges.
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 dataAudit and harden /etc/sudoers files in Kolla containers to follow least-privilege principles; remove unnecessary sudo permissions and avoid allowing root-level commands without authentication.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38060 — 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-2022-38060 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