CVE-2023-48910 — microcks
CRITICALCVE-2023-48910 is a critical-severity (CVSS 9.8) Server-Side Request Forgery (SSRF) vulnerability in io.github.microcks:microcks. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for io.github.microcks:microcks — see the affected versions and patch details below.
Microcks contains a Server-Side Request Forgery (SSRF) via the component /jobs and /artifact/download
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-48910.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.github.microcks:microcksReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Microcks up to version 1.17.1 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /jobs and /artifact/download. This vulnerability allows attackers to access network resources and sensitive information via a crafted GET request.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.github.microcks:microcks | all versions | 1.17.1io.github.microcks:microcks:1.17.1 |
Affected Products
microcksmicrocksResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.microcks:microcks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.github.microcks:microcks to 1.17.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-48910 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2023-48910 in your dependencies?
Find it across Maven, including transitive dependencies.