# CVE-2023-52354: chasquid HTTP Request/Response Smuggling vulnerability

> An attacker can bypass SMTP security checks by sending LF-terminated lines, potentially allowing email spoofing or policy evasion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** DEBIAN-CVE-2023-52354, GHSA-g4x3-mfpj-f335, GO-2024-2478, UBUNTU-CVE-2023-52354

## What is CVE-2023-52354?

CVE-2023-52354 is a high-severity vulnerability in n/a, published on 22 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

chasquid before 1.13 allows SMTP smuggling because LF-terminated lines are accepted.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2023-52354?

3 open source packages ship an affected version, including github.com/albertito/chasquid and blitiri.com.ar/go/chasquid. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/albertito/chasquid` | Go | All versions | 1.13 |
| `github.com/albertito/chasquid` | Go | All versions | 1.13 |
| `blitiri.com.ar/go/chasquid` | Go | All versions | 1.13.0 |

Products: Blitiri Chasquid.

## How do I fix CVE-2023-52354?

Upgrade github.com/albertito/chasquid to 1.13 or later.

## Is CVE-2023-52354 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52354 and fix it if it is affected.

What it is: CVE-2023-52354 is a high-severity vulnerability in n/a, published on 22 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52354 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/albertito/chasquid (Go): affected all versions; fixed in 1.13
- github.com/albertito/chasquid (Go): affected all versions; fixed in 1.13
- blitiri.com.ar/go/chasquid (Go): affected all versions; fixed in 1.13.0

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-2023-52354/ (Markdown: https://insights.sbomify.com/CVE-2023-52354/index.md)
```

## Sources

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

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