# CVE-2023-42361: Path traversal in n/a

> An attacker can view arbitrary files on the server by using a crafted image during PDF export in the Better PDF Exporter plugin for Jira.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Nov 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-xhj7-pf22-5x9w

## What is CVE-2023-42361?

CVE-2023-42361 is a high-severity path traversal vulnerability in n/a, published on 7 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Local File Inclusion vulnerability in Midori-global Better PDF Exporter for Jira Server and Jira Data Center v.10.3.0 and before allows an attacker to view arbitrary files and cause other impacts via use of crafted image during PDF export.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Midori-Global Better Pdf Exporter.

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

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

## Is CVE-2023-42361 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36131](https://insights.sbomify.com/CVE-2022-36131/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42361 is a high-severity path traversal vulnerability in n/a, published on 7 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-42361 in the wild and no public exploit code.

Affected product: n/a. 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-2023-42361/ (Markdown: https://insights.sbomify.com/CVE-2023-42361/index.md)
```

## Sources

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

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