# CVE-2020-29659: Memory corruption in n/a

> Remote attackers can execute arbitrary code with SYSTEM privileges via a buffer overflow in the web server's sid parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 9 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-88h9-g339-rxgm

## What is CVE-2020-29659?

CVE-2020-29659 is a critical memory corruption vulnerability in n/a, published on 9 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow in the web server of Flexense DupScout Enterprise 10.0.18 allows a remote anonymous attacker to execute code as SYSTEM by overflowing the sid parameter via a GET /settings&sid= attack.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Flexense Dupscout.

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

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

## Is CVE-2020-29659 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10566](https://insights.sbomify.com/CVE-2018-10566/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29659 is a critical memory corruption vulnerability in n/a, published on 9 Dec 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-29659 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-29659/ (Markdown: https://insights.sbomify.com/CVE-2020-29659/index.md)
```

## Sources

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

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