Cyber Resilience

CVE-2024-38522

Hushline Hush Line ≤ 0.1.0

Public PoC
Published
28 June 2024
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 6.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
EPSS Score 0.0035 28th percentile
Risk Priority 48 floored blend · peak EPSS

Summary

CVE-2024-38522 is a medium-severity Permissive List of Allowed Inputs (CWE-183) vulnerability in Hushline Hush Line. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Obfuscated Files or Information (T1027); ranked at the 28th percentile by exploit likelihood (below the median); 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Hush Line is a free and open-source, anonymous-tip-line-as-a-service for organizations or individuals. The CSP policy applied on the `tips.hushline.app` website and bundled by default in this repository is trivial to bypass. This vulnerability has been patched in version 0.1.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38521Same product: Hushline Hush Line
CVE-2024-39534Shared CWE-697
CVE-2023-23766Shared CWE-697
CVE-2025-12192Shared CWE-697
CVE-2023-46009Shared CWE-697
CVE-2023-33225Shared CWE-697
CVE-2024-24621Shared CWE-697
CVE-2023-49994Shared CWE-697
CVE-2020-5849Shared CWE-697
CVE-2024-23903Shared CWE-697

Affected Assets

hushline
hush line
≤ 0.1.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)
  • V1.5.2
  • V4.4.2

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation directly exercises security-relevant comparisons to discover incorrect logic.

Strict validity checks on inputs directly stop overly permissive allow lists from being used as the protection mechanism.

A reference monitor must be small and correct, structurally limiting the chance of flawed comparison logic in authorization decisions.

Security engineering principles require correct implementation of comparison logic used for access and authentication decisions.

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 require rigorous allow-list design and testing that prevents permissive input validation.

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 can detect overly broad allow-lists, but does not inherently prevent their creation.

prevents

Secure development lifecycle includes code review and testing that can catch incorrect comparison logic.

prevents

Application security requirements can mandate strict, minimal allow-lists and input validation rules that prevent overly permissive lists.

prevents

Secure system architecture and engineering principles require explicit, least-privilege input validation designs that directly address permissive allow-lists.

prevents

Secure coding standards enforce rigorous input validation and reject unsafe values, mitigating permissive allow-list weaknesses.

degrades

Secure authentication mechanisms rely on correct comparison of credentials or tokens.

References