# CVE-2023-5016: spider-flow API DataSourceController.java DriverManager.getConnection deserialization

> Remote attackers can achieve code execution via unsafe deserialization in the DataSourceController API of spider-flow.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-f2mp-x3rj-623w

## What is CVE-2023-5016?

CVE-2023-5016 is a medium-severity unsafe deserialization vulnerability in spider-flow, published on 17 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in spider-flow up to 0.5.0. It has been declared as critical. Affected by this vulnerability is the function DriverManager.getConnection of the file src/main/java/org/spiderflow/controller/DataSourceController.java of the component API. The manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-239857 was assigned to this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Ssssssss Spider-Flow.

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

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

## Is CVE-2023-5016 being exploited?

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

## Other vulnerabilities in spider-flow

- [CVE-2024-0195](https://insights.sbomify.com/CVE-2024-0195/): spider-flow FunctionController.java FunctionService.saveFunction code injection (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5016 is a medium-severity unsafe deserialization vulnerability in spider-flow, published on 17 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5016 in the wild and no public exploit code.

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

## Sources

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

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