# CVE-2019-16753: Weak cryptography in n/a

> Weak signature scheme allows signature reuse across different message types, potentially enabling transaction forgery in DAPS and PIVX.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 4 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3r42-8xcq-6f4v

## What is CVE-2019-16753?

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

### Official description

An issue was discovered in Decentralized Anonymous Payment System (DAPS) through 2019-08-26. The content to be signed is composed of a representation of strings, rather than being composed of their binary representations. This is a weak signature scheme design that would allow the reuse of signatures in some cases (or even the reuse of signatures, intended for one type of message, for another type). This also affects Private Instant Verified Transactions (PIVX) through 3.4.0.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 2 products.


Products: Decentralized Anonymous Payment System Project Decentralized Anonymous Payment System, Pivx Private Instant Verified Transactions.

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

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

## Is CVE-2019-16753 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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