# CVE-2018-19833: Missing authorization in n/a

> Attackers can seize ownership of the DDQ token contract due to missing caller identity checks in the ownership transfer function.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 31 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cq27-627w-27r3

## What is CVE-2018-19833?

CVE-2018-19833 is a high-severity missing authorization vulnerability in n/a, published on 31 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The owned function of a smart contract implementation for DDQ, an tradable Ethereum ERC20 token, allows attackers to change the owner of the contract, because the function does not check the caller's identity.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-19833?

It affects 1 product.


Products: Ddq Project Ddq.

## How do I fix CVE-2018-19833?

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

## Is CVE-2018-19833 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19833 and fix it if it is affected.

What it is: CVE-2018-19833 is a high-severity missing authorization vulnerability in n/a, published on 31 Dec 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-2018-19833 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-2018-19833/ (Markdown: https://insights.sbomify.com/CVE-2018-19833/index.md)
```

## Sources

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

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