{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2372 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-2372 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2372 is a high-severity vulnerability in n/a, published on 26 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-2372 and fix it if it is affected.\n\nWhat it is: CVE-2005-2372 is a high-severity vulnerability in n/a, published on 26 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-2372 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2005-2372/ (Markdown: https://insights.sbomify.com/CVE-2005-2372/index.md)","id":"CVE-2005-2372","markdown":"https://insights.sbomify.com/CVE-2005-2372/index.md","name":"CVE-2005-2372","record":{"aliases":["GHSA-h3q5-7899-7pxx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Forms","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by uploading malicious form files and referencing them via servlet parameters in Oracle Forms.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"forms","vendor":"oracle"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Oracle Forms 4.5 through 10g starts form executables from arbitrary directories and executes them as the Oracle or System user, which allows attackers to execute arbitrary code by uploading a malicious .fmx file and referencing it using an absolute pathname argument in the (1) form or (2) module parameters to f90servlet.","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":"File upload in n/a","id":"CVE-2005-2372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2005-2373"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2005-2371"},"products":["n/a"],"published":"2005-07-26","related":[{"cvss_score":10,"headline":"Auth bypass in Oracle Forms","id":"CVE-2026-83099","kev_date_added":null,"published":"2026-09-15"},{"cvss_score":9.8,"headline":"Auth bypass in Oracle Forms","id":"CVE-2026-83094","kev_date_added":null,"published":"2026-09-15"},{"cvss_score":9.8,"headline":"Auth bypass in Oracle Forms","id":"CVE-2026-83095","kev_date_added":null,"published":"2026-09-15"},{"cvss_score":9.8,"headline":"Auth bypass in Oracle Forms","id":"CVE-2026-83098","kev_date_added":null,"published":"2026-09-15"},{"cvss_score":9.8,"headline":"Auth bypass in Oracle Forms","id":"CVE-2026-83100","kev_date_added":null,"published":"2026-09-15"},{"cvss_score":9.8,"headline":"Auth bypass in Oracle Forms","id":"CVE-2026-83108","kev_date_added":null,"published":"2026-09-15"},{"cvss_score":9.1,"headline":"Auth bypass in Oracle Forms","id":"CVE-2026-83104","kev_date_added":null,"published":"2026-09-15"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by uploading malicious form files and referencing them via servlet parameters in Oracle Forms.","url":"https://insights.sbomify.com/CVE-2005-2372/"}