# CVE-2022-24862: Server-Side Request Forgery in Databasir

> Attackers can exploit a JDBC driver download verification flaw to perform Server-Side Request Forgery, potentially accessing internal resources or sensitive data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 20 Apr 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-r8m9-r74j-vc6m

## What is CVE-2022-24862?

CVE-2022-24862 is a high-severity server-side request forgery vulnerability in vran-dev databasir, published on 20 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Databasir is a team-oriented relational database model document management platform. Databasir 1.01 has Server-Side Request Forgery vulnerability. During the download verification process of a JDBC driver the corresponding JDBC driver download address will be downloaded first, but this address will return a response page with complete error information when accessing a non-existent URL. Attackers can take advantage of this feature for SSRF.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-24862?

It affects 1 product.


Products: Databasir Project Databasir.

## How do I fix CVE-2022-24862?

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

## Is CVE-2022-24862 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24862 exists.

## Other vulnerabilities in vran-dev databasir

- [CVE-2022-24860](https://insights.sbomify.com/CVE-2022-24860/): Databasir 1.01 has Use of Hard-coded Cryptographic Key vulnerability. (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24862 and fix it if it is affected.

What it is: CVE-2022-24862 is a high-severity server-side request forgery vulnerability in vran-dev databasir, published on 20 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24862 exists.

Affected product: vran-dev databasir. 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-2022-24862/ (Markdown: https://insights.sbomify.com/CVE-2022-24862/index.md)
```

## Sources

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

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