# CVE-2019-13097: Business logic in n/a

> Attackers can manipulate score parameters in Cat Runner Decorate Home, allowing unauthorized modification of user scores.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 22 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-768r-hhh3-rcg3

## What is CVE-2019-13097?

CVE-2019-13097 is a high-severity vulnerability in n/a, published on 22 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The application API of Cat Runner Decorate Home version 2.8.0 for Android does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable. Attackers can manipulate users' score parameters exchanged between client and server.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-13097?

It affects 1 product.


Products: Cat Runner\  Decorate Home Project.

## How do I fix CVE-2019-13097?

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

## Is CVE-2019-13097 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13097 and fix it if it is affected.

What it is: CVE-2019-13097 is a high-severity vulnerability in n/a, published on 22 Jul 2019. 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-2019-13097 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-2019-13097/ (Markdown: https://insights.sbomify.com/CVE-2019-13097/index.md)
```

## Sources

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

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