{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30556 exists.","fix":"No fix has been published for CVE-2023-30556 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-30556 is a medium-severity SQL injection vulnerability in hhyo Archery, published on 18 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-30556 and fix it if it is affected.\n\nWhat it is: CVE-2023-30556 is a medium-severity SQL injection vulnerability in hhyo Archery, published on 18 Apr 2023. 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-2023-30556 exists.\n\nAffected product: hhyo Archery. 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-30556/ (Markdown: https://insights.sbomify.com/CVE-2023-30556/index.md)","id":"CVE-2023-30556","markdown":"https://insights.sbomify.com/CVE-2023-30556/index.md","name":"CVE-2023-30556","record":{"aliases":["GHSA-6pv9-9gq7-hr68"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SQL audit platform","requires_auth":"low_privilege","summary":"Attackers can inject SQL via the db_name parameter to query connected databases in the Archery SQL audit platform.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"archery","vendor":"archerydms"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Archery is an open source SQL audit platform. The Archery project contains multiple SQL injection vulnerabilities, that may allow an attacker to query the connected databases. Affected versions are subject to SQL injection in the `optimize_sqltuningadvisor` method of `sql_optimize.py`. User input coming from the `db_name` parameter value in `sql_optimize.py` is passed to the `sqltuningadvisor` method in `oracle.py`for execution. To mitigate escape the variables accepted via user input when used in `sql_optimize.py`. Users may also use prepared statements when dealing with SQL as a mitigation for this issue. This issue is also indexed as `GHSL-2022-107`.","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":"SQL injection in sql_optimize.py optimize_sqltuningadvisor method in Archery - GHSL-2022-107","id":"CVE-2023-30556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in data_dictionary.py table_info method in Archery - GHSL-2022-106","id":"CVE-2023-30557"},"packages":[],"prev":{"headline":"SQL injection in sql_optimize.py explain method in Archery - GHSL-2022-108","id":"CVE-2023-30555"},"products":["Archery"],"published":"2023-04-18","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-38537","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-38538","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-38539","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-38540","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-38541","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-38542","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2023-48053","kev_date_added":null,"published":"2023-11-16"}],"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-02-05","vendors":["hhyo"]},"summary":"Attackers can inject SQL via the db_name parameter to query connected databases in the Archery SQL audit platform.","url":"https://insights.sbomify.com/CVE-2023-30556/"}