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

> A typo in the Owned contract constructor allows attackers to seize ownership, enabling free token acquisition and denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 30 Dec 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jmf4-pvqr-x2gx

## What is CVE-2019-15080?

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

### Official description

An issue was discovered in a smart contract implementation for MORPH Token through 2019-06-05, an Ethereum token. A typo in the constructor of the Owned contract (which is inherited by MORPH Token) allows attackers to acquire contract ownership. A new owner can subsequently obtain MORPH Tokens for free and can perform a DoS attack.

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

It affects 1 product.


Products: Morph Project Morph.

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

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

## Is CVE-2019-15080 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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