# OSV-2023-521: Security exception in com.code_intelligence.jazzer.sanitizers.ServerSideRequestForgery.checkSsrf

> A security exception in Jazzer's SSRF sanitizer allows bypassing Server-Side Request Forgery protections during fuzzing.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2023

## What is OSV-2023-521?

OSV-2023-521 is a server-side request forgery vulnerability in htmlunit, published on 29 Jun 2023. It can be exploited over the network, with no action from the victim.

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60179

```
Crash type: Security exception
Crash state:
com.code_intelligence.jazzer.sanitizers.ServerSideRequestForgery.checkSsrf
com.code_intelligence.jazzer.sanitizers.ServerSideRequestForgery.checkSsrfSocket
java.base/java.net.Socket.connect
```

## Which versions are affected by OSV-2023-521?

1 open source package ship an affected version, including htmlunit.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `htmlunit` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2023-521?

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

## Is OSV-2023-521 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2023-521 and fix it if it is affected.

What it is: OSV-2023-521 is a server-side request forgery vulnerability in htmlunit, published on 29 Jun 2023. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of OSV-2023-521 in the wild and no public exploit code.

Affected packages and fixed versions:
- htmlunit (OSS-Fuzz): affected all versions; no fix listed

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

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2023-521

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