# CVE-2024-38523: Hush Line OTP issue

> Attackers can bypass TOTP authentication to change security settings via CSRF or XSS, potentially taking over accounts in Hush Line.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4c38-hhxx-9mhx

## What is CVE-2024-38523?

CVE-2024-38523 is a high-severity authentication bypass vulnerability in scidsg hushline, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hush Line is a free and open-source, anonymous-tip-line-as-a-service for organizations or individuals. The TOTP authentication flow has multiple issues that weakens its one-time nature. Specifically, the lack of 2FA for changing security settings allows attacker with CSRF or XSS primitives to change such settings without user interaction and credentials are required. This vulnerability has been patched in version 0.10.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-38523?


## How do I fix CVE-2024-38523?

No fix has been published for CVE-2024-38523 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-38523 being exploited?

There is no known exploitation of CVE-2024-38523 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38523 and fix it if it is affected.

What it is: CVE-2024-38523 is a high-severity authentication bypass vulnerability in scidsg hushline, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38523 in the wild and no public exploit code.

Affected product: scidsg hushline. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-38523/ (Markdown: https://insights.sbomify.com/CVE-2024-38523/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38523
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38523
- OSV: https://osv.dev/vulnerability/CVE-2024-38523

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-38523/
Summaries are generated and may contain mistakes; the official description above is the record.