# CVE-2022-24860: Databasir 1.01 has Use of Hard-coded Cryptographic Key vulnerability.

> An attacker can use hard-coded cryptographic keys to generate login credentials and access the Databasir service background.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-9prp-5jc9-jpgg

## What is CVE-2022-24860?

CVE-2022-24860 is a high-severity vulnerability in vran-dev databasir, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Databasir is a team-oriented relational database model document management platform. Databasir 1.01 has Use of Hard-coded Cryptographic Key vulnerability. An attacker can use hard coding to generate login credentials of any user and log in to the service background located at different IP addresses.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 1 product.


Products: Databasir Project Databasir.

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

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

## Is CVE-2022-24860 being exploited?

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

## Other vulnerabilities in vran-dev databasir

- [CVE-2022-24862](https://insights.sbomify.com/CVE-2022-24862/): Server-Side Request Forgery in Databasir (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24860 is a high-severity vulnerability in vran-dev databasir, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24860 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-24860/ (Markdown: https://insights.sbomify.com/CVE-2022-24860/index.md)
```

## Sources

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

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