# CVE-2020-11883: Diavante vue-storefront-api and storefront-api disclose stack trace

> Attackers can trigger exceptions to reveal stack traces containing absolute file paths and module names, exposing internal system details.

- **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:** Yes
- **Published:** 17 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9wxj-37p8-49ff

## What is CVE-2020-11883?

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

### Official description

In Divante vue-storefront-api through 1.11.1 and storefront-api through 1.0-rc.1, as used in VueStorefront PWA, unexpected HTTP requests lead to an exception that discloses the error stack trace, with absolute file paths and Node.js module names.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

4 open source packages ship an affected version, including storefront-api and vue-storefront-api. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `storefront-api` | npm | All versions | 1.0.0-rc3 |
| `storefront-api` | npm | All versions | 1.0.0-rc3 |
| `vue-storefront-api` | npm | All versions | 1.12.0 |
| `vue-storefront-api` | npm | All versions | 1.12.0 |

Products: Divante Storefront-Api, Divante Vue-Storefront-Api.

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

Upgrade storefront-api to 1.0.0-rc3 or later.

## Is CVE-2020-11883 being exploited?

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

Public exploit code:

- vue-storefront-api vulnerability (github_poc): https://github.com/0ndras3k/CVE-2020-11883

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11883 is a medium-severity vulnerability in n/a, published on 17 Apr 2020. 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-11883 in the wild and no public exploit code.

Affected packages and fixed versions:
- storefront-api (npm): affected all versions; fixed in 1.0.0-rc3
- storefront-api (npm): affected all versions; fixed in 1.0.0-rc3
- vue-storefront-api (npm): affected all versions; fixed in 1.12.0
- vue-storefront-api (npm): affected all versions; fixed in 1.12.0

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-11883/ (Markdown: https://insights.sbomify.com/CVE-2020-11883/index.md)
```

## Sources

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

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