# CVE-2020-5799: Hardcoded credentials in Eat Spray Love

> A backdoor account in the Eat Spray Love mobile app allows attackers to gain privileged access and view other users' data.

- **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:** 7 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rcr9-98rj-4395

## What is CVE-2020-5799?

CVE-2020-5799 is a critical vulnerability in Eat Spray Love, published on 7 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Eat Spray Love mobile app for both iOS and Android contains a backdoor account that, when modified, allowed privileged access to restricted functionality and to other users' data.

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

It affects 1 product.


Products: Eat Spray Love Project Eat Spray Love.

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

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

## Is CVE-2020-5799 being exploited?

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

## Other vulnerabilities in Eat Spray Love

- [CVE-2020-5800](https://insights.sbomify.com/CVE-2020-5800/): Auth bypass in Eat Spray Love (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5799 is a critical vulnerability in Eat Spray Love, published on 7 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-5799 in the wild and no public exploit code.

Affected product: Eat Spray Love. 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-5799/ (Markdown: https://insights.sbomify.com/CVE-2020-5799/index.md)
```

## Sources

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

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