{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31196 exists.","fix":"No fix has been published for CVE-2022-31196 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31196 is a high-severity server-side request forgery vulnerability in vran-dev databasir, published on 2 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31196 and fix it if it is affected.\n\nWhat it is: CVE-2022-31196 is a high-severity server-side request forgery vulnerability in vran-dev databasir, published on 2 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31196 exists.\n\nAffected product: vran-dev databasir. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-31196/ (Markdown: https://insights.sbomify.com/CVE-2022-31196/index.md)","id":"CVE-2022-31196","markdown":"https://insights.sbomify.com/CVE-2022-31196/index.md","name":"CVE-2022-31196","record":{"aliases":["GHSA-qvg8-427f-852q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Database metadata platform","requires_auth":"low_privilege","summary":"Attackers can exploit SSRF in Databasir to scan intranets and obtain real IP addresses by sending a crafted HTTP POST request.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"databasir","vendor":"databasir"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Databasir is a database metadata management platform. Databasir \u003c= 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Server-Side Request Forgery (SSRF) vulnerability in Databasir","id":"CVE-2022-31196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"SQL Injection in ResultSet.refreshRow() with malicious column names in pgjdbc","id":"CVE-2022-31197"},"packages":[],"prev":{"headline":"Path traversal vulnerability in Simple Archive Format package import in DSpace","id":"CVE-2022-31195"},"products":["databasir"],"published":"2022-09-02","related":[{"cvss_score":9.9,"headline":"Remote Code Execution in Databasir","id":"CVE-2022-24861","kev_date_added":null,"published":"2022-04-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-66944","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-27821","kev_date_added":null,"published":"2023-03-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["vran-dev"]},"summary":"Attackers can exploit SSRF in Databasir to scan intranets and obtain real IP addresses by sending a crafted HTTP POST request.","url":"https://insights.sbomify.com/CVE-2022-31196/"}