# CVE-2018-12557: Information disclosure in n/a

> Zuul may leak credentials or secrets in console logs when nodes go offline during looped tasks, exposing sensitive data to anyone with log access.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-33rx-8w5x-4jgv

## What is CVE-2018-12557?

CVE-2018-12557 is a critical vulnerability in n/a, published on 19 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-12557?

It affects 1 product.


Products: Zuul-Ci Zuul.

## How do I fix CVE-2018-12557?

No fix has been published for CVE-2018-12557 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-12557 being exploited?

There is no known exploitation of CVE-2018-12557 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12557 and fix it if it is affected.

What it is: CVE-2018-12557 is a critical vulnerability in n/a, published on 19 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12557 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-12557/ (Markdown: https://insights.sbomify.com/CVE-2018-12557/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-12557
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-12557
- OSV: https://osv.dev/vulnerability/CVE-2018-12557

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-12557/
Summaries are generated and may contain mistakes; the official description above is the record.