CVE-2024-38522
Hushline Hush Line ≤ 0.1.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
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 OS Credential Dumping (T1003); ranked at the 27th 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
- 🇪🇺 ENISA EUVD: EUVD-2024-37391
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
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.2V4.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.
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.
Secure development lifecycle includes code review and testing that can catch incorrect comparison logic.
Application security requirements can mandate strict, minimal allow-lists and input validation rules that prevent overly permissive lists.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, secure session control, data validation/sanitization, assume-breach) that reach many but not all permissive-allowlist cases; a bounded remainder (e.g. custom business-logic allowlists whose enumerated safe values are chosen incorrectly) can still be introduced and exploited.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-697, a pillar-level weakness, and none of its children carries one either.