OSV-2023-521
Security exception in com.code_intelligence.jazzer.sanitizers.ServerSideRequestForgery.checkSsrf
No scoreFix available
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
What each source reports
OSV No score
Security exception in com.code_intelligence.jazzer.sanitizers.ServerSideRequestForgery.checkSsrf
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
- Record
OSV-2023-521- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
htmlunitOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2023-521 is a vulnerability with no CVSS score yet in htmlunit, published June 29, 2023. No source lists public exploit code. A source reports a fix.