dbcve.org
OpenstackApplication · Redhat

CVE-2022-3101

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
A flaw was found in tripleo-ansible. Due to an insecure default configuration, the permissions of a sensitive file are not sufficiently restricted. This flaw allows a local attacker to use brute force to explore the relevant directory and discover the file, leading to information disclosure of important configuration details from the OpenStack deployment.

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 confidence

A vulnerability in tripleo-ansible allows local attackers to discover a sensitive file with overly permissive access permissions. Due to an insecure default configuration, the file's permissions are insufficiently restricted, enabling brute-force directory exploration to reveal important OpenStack deployment configuration details.

MitigationRestrict file permissions on the sensitive configuration file (e.g., chmod 600 or more restrictive) and update the default configuration in tripleo-ansible to use secure permissions.

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
Affected:= 16.1= 16.2
Openstack For Ibm PowerApplication
Affected:= 16.1= 16.2
Tripleo AnsibleApplication
Affected:all versions

CVSS 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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if tripleo-ansible is installed
    Run 'rpm -qa | grep tripleo-ansible' or 'pip list | grep tripleo-ansible' to see if the tripleo-ansible package is present on the system
    Affected if The package is installed and the version falls within the affected ranges or is any version of Openstack Tripleo Ansible
  2. Locate tripleo-ansible configuration directories
    Search for directories containing 'tripleo' or 'tripleo-ansible' in common paths such as /etc, /opt, /home, or the user's working directory. Use 'find / -type d -name '*tripleo*' 2>/dev/null' to discover these directories
    Affected if Any tripleo-ansible configuration or working directories exist on the system
  3. Check file permissions on sensitive configuration files
    Within the tripleo-ansible directories, identify configuration files (commonly YAML, YAML.j2, or conf files) and inspect their permissions using 'ls -la <file>'. Look for files with permissions 644, 666, or other overly permissive settings (readable by others or world-readable)
    Affected if Any configuration file containing deployment details such as passwords, tokens, credentials, or network configurations has permissions that allow reading by non-owner users (e.g., mode 644, 664, or 666)
  4. Search for files with world-readable permissions
    Run 'find <tripleo-directory> -type f -perm -004 2>/dev/null' to find all files readable by others within the tripleo-ansible directories
    Affected if Sensitive configuration or credential files are found with world-readable permissions (mode includes 4 or higher for others)
  5. Inspect default configuration templates
    Examine Jinja2 templates (files ending in .j2) and configuration defaults in the tripleo-ansible installation for any file paths referenced and verify their default permissions by checking the surrounding Ansible roles or playbooks
    Affected if The default configuration references a file path that is created with permissive default permissions (world-readable or group-readable)

The system is affected if tripleo-ansible is installed and any configuration file containing sensitive OpenStack deployment details (credentials, passwords, tokens, network configuration) is readable by non-owner users due to overly permissive file permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict file permissions on the sensitive configuration file (e.g., chmod 600 or more restrictive) and update the default configuration in tripleo-ansible to use secure permissions.

Recommended fix Moderate confidence

Red Hat OpenStack Platform 16.3 or later (or latest available update containing the CVE-2022-3101 fix)

  1. Check for available Red Hat Security Advisories (RHSA) related to CVE-2022-3101 by running: sudo yum updateinfo list security CVE-2022-3101
  2. If a security update is available, apply it by running: sudo yum update
  3. Alternatively, upgrade Red Hat OpenStack Platform to version 16.3 or later which contains the fix
  4. For Tripleo Ansible, ensure all tripleo-ansible packages are updated to the fixed version
  5. After update, verify the fix by checking that the sensitive file permissions are properly restricted (e.g., chmod 600 or more restrictive on sensitive configuration files)
  6. Consult the official Red Hat Security Advisory for this CVE at access.redhat.com for complete patch details
Caveat Standard upgrade precautions apply - test in staging environment first, ensure backups are current, and verify compatibility with dependent components

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openstack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3101 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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