# CVE-2023-42508: JFrog Artifactory Improper header input validation leads to email manipulation sent from the platform

> Unauthenticated attackers can manipulate email bodies sent by JFrog Artifactory via crafted payloads, requiring an upgrade to remediate.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** BIT-artifactory-2023-42508, GHSA-mp3m-h3mq-83jw

## What is CVE-2023-42508?

CVE-2023-42508 is a medium-severity vulnerability in Jfrog Artifactory, published on 3 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

JFrog Artifactory prior to version 7.66.0 is vulnerable to specific endpoint abuse with a specially crafted payload, which can lead to unauthenticated users being able to send emails with manipulated email body.

Weakness: CWE-20 (Improper Input Validation)

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

1 open source package ship an affected version, including artifactory. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `artifactory` | Bitnami | From 7.0.0 | 7.66.0 |

Products: Jfrog Artifactory.

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

Upgrade artifactory to 7.66.0 or later.

## Is CVE-2023-42508 being exploited?

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

## Other vulnerabilities in Jfrog Artifactory

- [CVE-2026-82329](https://insights.sbomify.com/CVE-2026-82329/): JFrog Artifactory Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2026-42016](https://insights.sbomify.com/CVE-2026-42016/): JFrog Artifactory Incorrect Authorization (high 8.1, exploited in the wild)
- [CVE-2026-42018](https://insights.sbomify.com/CVE-2026-42018/): JFrog Artifactory Improper Authentication (high 7.5, exploited in the wild)
- [CVE-2026-66384](https://insights.sbomify.com/CVE-2026-66384/): JFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory (medium 5.3, exploited in the wild)
- [CVE-2019-17444](https://insights.sbomify.com/CVE-2019-17444/): JFrog Artifactory does not enforce default admin password change (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42508 is a medium-severity vulnerability in Jfrog Artifactory, published on 3 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-42508 in the wild and no public exploit code.

Affected packages and fixed versions:
- artifactory (Bitnami): affected from 7.0.0; fixed in 7.66.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-42508/ (Markdown: https://insights.sbomify.com/CVE-2023-42508/index.md)
```

## Sources

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

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