ansible vulnerabilities

Browse known CVEs and advisories by package and ecosystem. Severity tells you the worst case. What determines real risk is whether the vulnerable code actually runs in your applications.

Browse by ecosystem

npm PyPI Maven Go RubyGems Cargo NuGet Composer pub Swift GitHub Actions

CVE-IDSeverityPackage summary

CVE-2020-10685Mediumansible: Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible CVE-2020-1735Mediumansible: Path Traversal in Ansible CVE-2020-1753Mediumansible: Insertion of Sensitive Information into Log File, Invocation of Process Using Visible Sensitive Information, and Exposure of Sensitive…CVE-2020-1739Lowansible: Exposure of Sensitive Information to an Unauthorized Actor in Ansible CVE-2019-14864Mediumansible: Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible CVE-2019-10156Mediumansible: Exposure of Sensitive Information to an Unauthorized Actor in ansible CVE-2019-3828Lowansible: Ansible Path Traversal vulnerability CVE-2015-3908Highansible: Ansible does not verify that the server hostname matches a domain name in certificates CVE-2016-3096Highansible: Link Following in ansible CVE-2013-2233Criticalansible: Ansible fails to cache SSH host keys CVE-2016-8647Mediumansible: Improper Input Validation in ansible CVE-2016-8614Highansible: Ansible apt_key module does not properly verify key fingerprint CVE-2018-10855Highansible: Ansible exposes sensitive data in log files and on the terminal CVE-2016-8628Criticalansible: Ansible fails to properly sanitize fact variables sent from the Ansible controller CVE-2016-9587Criticalansible: Ansible is vulnerable to an improper input validation in Ansible's handling of data sent from client systems CVE-2017-7481Criticalansible: Ansible fails to properly mark lookup-plugin results as unsafe

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo

Get a personalized demo