# CVE-2023-5786: GeoServer GeoWebCache rest.html direct request

> Remote attackers can access the GeoWebCache REST interface without proper authorization, potentially exposing sensitive configuration data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-382v-j99g-hw2p

## What is CVE-2023-5786?

CVE-2023-5786 is a medium-severity missing authorization vulnerability in GeoServer GeoWebCache, published on 26 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in GeoServer GeoWebCache up to 1.15.1. It has been declared as problematic. This vulnerability affects unknown code of the file /geoserver/gwc/rest.html. The manipulation leads to direct request. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-243592.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Geoserver Geowebcache.

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

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

## Is CVE-2023-5786 being exploited?

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

## Other vulnerabilities in GeoServer GeoWebCache

- [CVE-2022-24846](https://insights.sbomify.com/CVE-2022-24846/): Unchecked JNDI lookups in GeoWebCache (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5786 is a medium-severity missing authorization vulnerability in GeoServer GeoWebCache, published on 26 Oct 2023. 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-5786 in the wild and no public exploit code.

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

## Sources

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

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