CVE-2021-20180

A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.

Published: 2022-03-16 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-20180 is rated Low Risk (29.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.30%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-20180

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.04% 0.30% +0.26%
2 2026-01-05 0.06% 0.04% -0.02%
3 2025-08-22 — 0.06% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-20180

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 3.9 2.9 [email protected]

Weakness enumeration for CVE-2021-20180

GitHub Security Advisory for CVE-2021-20180

GHSA-fh5v-5f35-2rv2 · Severity: medium · Ecosystem: pip — Insertion of Sensitive Information into Log File in ansible

OS Trackers for CVE-2021-20180

vendor priority summary link
debian not yet assigned CVE-2021-20180 not yet assigned priority: Debian including 1 source packages (ansible), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2021-20180
redhat medium — https://access.redhat.com/security/cve/CVE-2021-20180
suse medium — https://www.suse.com/security/cve/CVE-2021-20180/
ubuntu medium CVE-2021-20180 medium priority: Ubuntu including 1 source packages (ansible), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 8, needs-triage 8. https://ubuntu.com/security/CVE-2021-20180

Affected software / configurations for CVE-2021-20180

Vendor Product Version Raw CPE
redhat ansible < 2.9.18 cpe:2.3:a:redhat:ansible:*:*:*:*:*:*:*:*

References for CVE-2021-20180

URL Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1915808 Issue Tracking Vendor Advisory
cvelogic Threat Intelligence