{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3731 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-3731 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3731 is a medium-severity SQL injection vulnerability in seccome Ehoney, published on 28 Oct 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-3731 and fix it if it is affected.\n\nWhat it is: CVE-2022-3731 is a medium-severity SQL injection vulnerability in seccome Ehoney, published on 28 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-3731 in the wild and no public exploit code.\n\nAffected product: seccome Ehoney. 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-3731/ (Markdown: https://insights.sbomify.com/CVE-2022-3731/index.md)","id":"CVE-2022-3731","markdown":"https://insights.sbomify.com/CVE-2022-3731/index.md","name":"CVE-2022-3731","record":{"aliases":["GHSA-rh3c-6gpv-2c72"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ehoney honeypot","requires_auth":"low_privilege","summary":"Remote attackers can exploit SQL injection in the Ehoney token API to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ehoney","vendor":"ehoney_project"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-707","name":"Improper Neutralization"}],"description":"A vulnerability has been found in seccome Ehoney and classified as critical. Affected by this vulnerability is an unknown functionality of the file /api/v1/attack/token. The manipulation of the argument Payload leads to sql injection. The attack can be launched remotely. The identifier VDB-212413 was assigned to this vulnerability.","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":"seccome Ehoney token sql injection","id":"CVE-2022-3731","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"seccome Ehoney set sql injection","id":"CVE-2022-3732"},"packages":[],"prev":{"headline":"seccome Ehoney falco sql injection","id":"CVE-2022-3730"},"products":["Ehoney"],"published":"2022-10-28","related":[{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-38868","kev_date_added":null,"published":"2023-02-15"},{"cvss_score":6.3,"headline":"seccome Ehoney attack sql injection","id":"CVE-2022-3729","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":6.3,"headline":"seccome Ehoney falco sql injection","id":"CVE-2022-3730","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":6.3,"headline":"seccome Ehoney set sql injection","id":"CVE-2022-3732","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":6.3,"headline":"seccome Ehoney signup access control","id":"CVE-2022-3735","kev_date_added":null,"published":"2022-10-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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["seccome"]},"summary":"Remote attackers can exploit SQL injection in the Ehoney token API to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2022-3731/"}