# CVE-2020-29041: Information disclosure in n/a

> Unauthenticated attackers can download source maps revealing source code and API keys due to misconfigured production Webpack settings.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q949-6jcq-74v3

## What is CVE-2020-29041?

CVE-2020-29041 is a medium-severity vulnerability in n/a, published on 6 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A misconfiguration in Web-Sesame 2020.1.1.3375 allows an unauthenticated attacker to download the source code of the application, facilitating its comprehension (code review). Specifically, JavaScript source maps were inadvertently included in the production Webpack configuration. These maps contain sources used to generate the bundle, configuration settings (e.g., API keys), and developers' comments.

## Which versions are affected by CVE-2020-29041?

It affects 1 product.


Products: Sesame-System Web-Sesame.

## How do I fix CVE-2020-29041?

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

## Is CVE-2020-29041 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-29041 and fix it if it is affected.

What it is: CVE-2020-29041 is a medium-severity vulnerability in n/a, published on 6 Jan 2021. 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-2020-29041 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-2020-29041/ (Markdown: https://insights.sbomify.com/CVE-2020-29041/index.md)
```

## Sources

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

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