An issue was discovered in Zuul 3.x before 3.1.0. If nodes become offline during the build, the no_log attribute of a task is ignored. If the unreachable error occurred in a task used with a loop variable (e.g., with_items), the contents of the loop items would be printed in the console. This could lead to accidentally leaking credentials or secrets.
References
Link | Resource |
---|---|
http://lists.zuul-ci.org/pipermail/zuul-announce/2018-June/000015.html | Mailing List Vendor Advisory |
https://git.zuul-ci.org/cgit/zuul/commit/?id=ffe7278c08e6e36bf8b18f732c764e00ff51551e | Patch Vendor Advisory |
https://storyboard.openstack.org/#%21/story/2002177 |
Configurations
History
No history.
Information
Published : 2018-06-19 05:29
Updated : 2024-02-04 19:46
NVD link : CVE-2018-12557
Mitre link : CVE-2018-12557
CVE.ORG link : CVE-2018-12557
JSON object : View
Products Affected
zuul-ci
- zuul
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor