CVE-2018-19156: High severity PIVX PIVX vulnerability

Q: What does an attacker need to exploit this issue?

The attacker needs to acquire even a small amount of PIVX stake or coins. They can then remotely send invalid headers or blocks to victims; no victim interaction is required.

Q: What is the operational impact on affected nodes?

Affected nodes store the attacker-supplied invalid headers or blocks on disk. This can consume disk storage and cause a denial of service.

Q: Which PIVX versions are identified as affected?

PIVX through version 3.1.03 is identified as affected. The provided data does not identify a fixed version.

Published Nov 5, 2019

Updated

PIVX through 3.1.03 (a chain-based proof-of-stake cryptocurrency) allows a remote denial of service, exploitable by an attacker who acquires even a small amount of stake/coins in the system. The attacker sends invalid headers/blocks, which are stored on the victim's disk.

Affected Software

1 affected component

PIVX PIVX<=3.1.03

Event History

Nov 5, 2019

CVE Published

via MITRE·08:07 PM

Data Sourced

via MITRE·08:07 PM

Description

Frequently Asked Questions

What does an attacker need to exploit this issue?

The attacker needs to acquire even a small amount of PIVX stake or coins. They can then remotely send invalid headers or blocks to victims; no victim interaction is required.

What is the operational impact on affected nodes?

Affected nodes store the attacker-supplied invalid headers or blocks on disk. This can consume disk storage and cause a denial of service.

Which PIVX versions are identified as affected?

PIVX through version 3.1.03 is identified as affected. The provided data does not identify a fixed version.

CVE-2018-19156: High severity PIVX PIVX vulnerability

Affected Software

Event History

Frequently Asked Questions

What does an attacker need to exploit this issue?

What is the operational impact on affected nodes?

Which PIVX versions are identified as affected?

Company

Resources

Contact

Frequently Asked Questions

What does an attacker need to exploit this issue?

What is the operational impact on affected nodes?

Which PIVX versions are identified as affected?