CVE-2022-31196 json
Server-Side Request Forgery (SSRF) vulnerability in Databasir
published 2022-09-02 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-52784
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
Databasir is a database metadata management platform. Databasir <= 1.06 has Server-Side Request Forgery (SSRF) vulnerability. The SSRF is triggered by a sending a **single** HTTP POST request to create a databaseType. By supplying a `jdbcDriverFileUrl` that returns a non `200` response code, the url is executed, the response is logged (both in terminal and in database) and is included in the response. This would allow an attackers to obtain the real IP address and scan Intranet information. This issue was fixed in version 1.0.7.
Patch / fix
- databasir databasir 1.0.7
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.06% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/vran-dev/databasir/security/advisories/GHSA-qvg8-427f-852q referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- vran-dev databasir
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/vran-dev/databasir/commit/226c20e0c9124037671a91d6b3e5083bd2462058
patch, third-party-advisory
-
github.com
/vran-dev/databasir/security/advisories/GHSA-qvg8-427f-852q
exploit, third-party-advisory
-
github.com
/vran-dev/databasir/releases/tag/v1.0.7
release-notes, third-party-advisory
Sources
- CVE List CVE-2022-31196
- NVD CVE-2022-31196
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.