{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-3377 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-3377 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3377 is a critical SQL injection vulnerability in Veribilim Software Computer Veribase, published on 23 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-3377 and fix it if it is affected.\n\nWhat it is: CVE-2023-3377 is a critical SQL injection vulnerability in Veribilim Software Computer Veribase, published on 23 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-3377 in the wild and no public exploit code.\n\nAffected product: Veribilim Software Computer Veribase. 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-2023-3377/ (Markdown: https://insights.sbomify.com/CVE-2023-3377/index.md)","id":"CVE-2023-3377","markdown":"https://insights.sbomify.com/CVE-2023-3377/index.md","name":"CVE-2023-3377","record":{"aliases":["GHSA-fxxw-g3mj-8gjg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Veribase software","requires_auth":"none","summary":"SQL injection in Veribase allows attackers to read or modify database contents; vendor did not respond to disclosure.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TR-CERT","cpe":[{"product":"veribase","vendor":"veribase"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Veribilim Software Computer Veribase allows SQL Injection.\n\nThis issue affects Veribase: through 20231123. \n\nNOTE: The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQLi in Veribilim's Veribase","id":"CVE-2023-3377","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2023-3378"},"packages":[],"prev":{"headline":"SQLi in Digital Strategys Zekiweb","id":"CVE-2023-3376"},"products":["Veribase"],"published":"2023-11-23","related":[],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-22","vendors":["Veribilim Software Computer"]},"summary":"SQL injection in Veribase allows attackers to read or modify database contents; vendor did not respond to disclosure.","url":"https://insights.sbomify.com/CVE-2023-3377/"}