dbcve.org
OpenstackApplication · Redhat

CVE-2022-3146

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. This issue leads 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

In tripleo-ansible, an insecure default configuration fails to sufficiently restrict permissions on a sensitive file (likely containing deployment credentials or configuration). A local attacker with filesystem access can use brute force enumeration to discover this file and read its contents, leading to disclosure of important OpenStack deployment configuration details.

MitigationConfigure proper restrictive file permissions (e.g., 600 or 640) on the sensitive file and ensure the default configuration in tripleo-ansible enforces these permissions; audit deployment scripts to remove overly permissive defaults.

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 the sensitive file in the TripleO deployment
    Locate the file containing deployment credentials or configuration in the tripleo-ansible deployment directory. Common locations include /home/stack, /etc/tripleo, or the tripleo-heat-templates directory. Look for files named passwords.yaml, userpass.yml, or similar credential-related files.
    Affected if The sensitive file exists and contains deployment credentials or configuration data.
  2. Check file permissions on the sensitive file
    Run 'ls -la <path_to_sensitive_file>' to view the file's permission bits. Look for permissions like 644, 655, or any setting that allows read access beyond the owner or intended group.
    Affected if Permissions are 644, 655, or any setting where 'others' have read permission (last digit is 4 or 5, or group has read).
  3. Verify world-readable access
    Run 'getfacl <path_to_sensitive_file>' or 'stat <path_to_sensitive_file>' to confirm if the file is accessible by any local user on the system.
    Affected if The file reports read access for 'other' or world-readable permissions are present.
  4. Confirm tripleo-ansible default configuration
    Review the default configuration files in /usr/share/tripleo-heat-templates or /opt/tripleo to see if they reference or create the sensitive file with permissive defaults. Check ansible roles and playbooks for file permission settings.
    Affected if Default configuration files set file permissions to 644 or higher without restrictive ownership.

A user is affected if the sensitive credential/configuration file in their tripleo-ansible deployment has permissions allowing read access by non-owner users (world-readable or group-readable).

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure proper restrictive file permissions (e.g., 600 or 640) on the sensitive file and ensure the default configuration in tripleo-ansible enforces these permissions; audit deployment scripts to remove overly permissive defaults.

Fix this in Openstack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3146 — 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-3146 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