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

Q: How do I fix CVE-2019-15080?

morph: upgrade to newer than 2019-06-05. Exact commands for each OS are on this page.

Q: Is CVE-2019-15080 being exploited?

CVE-2019-15080 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-15080 affect?

CVE-2019-15080 affects morph. Severity is high (CVSS 7.5). 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 owner

Q: How urgent is CVE-2019-15080?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2019-15080 is a high-severity flaw (CVSS 7.5) affecting morph. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Published	2020-12-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: morph project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-30 20:15 UTCPublished CVE record published
2026-06-17 02:19 UTCUpdated Record last modified

morph project morph UPGRADE

Affected: <= 2019-06-05

Fixed in: newer than 2019-06-05

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy morph || rpm -q morph || morph --version

2. UPGRADE to newer than 2019-06-05 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade morph

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade morph

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-15080?

morph: upgrade to newer than 2019-06-05. Exact commands for each OS are on this page.

Is CVE-2019-15080 being exploited?

CVE-2019-15080 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-15080 affect?

CVE-2019-15080 affects morph. Severity is high (CVSS 7.5). 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 owner

How urgent is CVE-2019-15080?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs