CVE-2024-33428

Stsaz Phiola remote code execution

8.8 HIGHPublic exploitEPSS 1.16%

Published1 May 2024

Description

Buffer-Overflow vulnerability at conv.c:68 of stsaz phiola v2.0-rc22 allows a remote attacker to execute arbitrary code via the a crafted .wav file.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Stsaz Phiola2.0

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

Patch & vendor advisories

https://github.com/stsaz/phiola/issues/29

References

https://github.com/Helson-S/FuzzyTesting/blob/master/phiola/heap-buffer-overflow-1/heap-buffer-overflow-1.assets/image-20240420005017430.pngExploitThird Party Advisory
https://github.com/Helson-S/FuzzyTesting/blob/master/phiola/heap-buffer-overflow-1/heap-buffer-overflow-1.mdExploitThird Party Advisory
https://github.com/Helson-S/FuzzyTesting/blob/master/phiola/heap-buffer-overflow-1/pocExploit
https://github.com/Helson-S/FuzzyTesting/tree/master/phiola/heap-buffer-overflow-1Exploit
https://github.com/stsaz/phiola/issues/29ExploitIssue TrackingVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-33428 being actively exploited?

CVE-2024-33428 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.16%.

How severe is CVE-2024-33428?

CVE-2024-33428 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 1.16% probability of exploitation.

Which products are affected by CVE-2024-33428?

Affected products include Stsaz Phiola.

How do I fix CVE-2024-33428?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-33428 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.