Cyber Resilience

CVE-2024-33431

Stsaz Phiola 2.0

Public PoC
Published
01 May 2024
Modified
19 September 2025
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0089 56th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

CVE-2024-33431 is a medium-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Stsaz Phiola. Its CVSS base score is 6.5 (Medium).

Operationally, ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An issue in phiola/src/afilter/conv.c:115 of phiola v2.0-rc22 allows a remote attacker to cause a denial of service via a crafted .wav file.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-33429Same product: Stsaz Phiola
CVE-2024-33430Same product: Stsaz Phiola
CVE-2024-33428Same product: Stsaz Phiola
CVE-2025-32996Shared CWE-670
CVE-2024-25622Shared CWE-670
CVE-2023-41058Shared CWE-670
CVE-2023-52781Shared CWE-670
CVE-2026-6608Shared CWE-670
CVE-2026-55276Shared CWE-670
CVE-2024-38365Shared CWE-670

Affected Assets

stsaz
phiola
2.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V9.2.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation at post-design stages directly exercises control-flow paths and reveals mismatches between implemented and intended behavior.

Requiring a documented development process and supporting tools reduces the chance that incorrect control-flow logic is introduced in the first place.

Flaw identification and remediation processes can locate and correct control-flow errors once they manifest as incorrect runtime behavior.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent incorrect control-flow implementations via reviews, testing, and static analysis.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect paths that deviate from intended logic.

prevents

Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.

prevents

Secure coding standards and reviews directly target flawed control-flow implementations.

prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References