{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2004-1339 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-1339 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-1339 is a medium-severity SQL injection vulnerability in Oracle Database Server, published on 6 Jan 2005. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-1339 and fix it if it is affected.\n\nWhat it is: CVE-2004-1339 is a medium-severity SQL injection vulnerability in Oracle Database Server, published on 6 Jan 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-2004-1339 in the wild and no public exploit code.\n\nAffected product: Oracle Database Server. 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-2004-1339/ (Markdown: https://insights.sbomify.com/CVE-2004-1339/index.md)","id":"CVE-2004-1339","markdown":"https://insights.sbomify.com/CVE-2004-1339/index.md","name":"CVE-2004-1339","record":{"aliases":["GHSA-7v5p-vcr4-vrxf"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Database","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary SQL commands via vulnerable database triggers, potentially compromising data integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"database_server","vendor":"oracle"},{"product":"oracle9i","vendor":"oracle"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection vulnerability in the (1) MDSYS.SDO_GEOM_TRIG_INS1 and (2) MDSYS.SDO_LRS_TRIG_INS default triggers in Oracle 9i and 10g allows remote attackers to execute arbitrary SQL commands via the new.table_name or new.column_name parameters.","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":"SQL injection in n/a","id":"CVE-2004-1339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:database_server","products":["oracle:database_server","oracle:oracle9i"],"type":"sql_injection","year":"2004"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2004-1340"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2004-1338"},"products":["n/a"],"published":"2005-01-06","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2015-4863","kev_date_added":null,"published":"2015-10-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2013-1534","kev_date_added":null,"published":"2013-04-17"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-0071","kev_date_added":null,"published":"2010-01-13"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-1979","kev_date_added":null,"published":"2009-10-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-1985","kev_date_added":null,"published":"2009-10-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-1992","kev_date_added":null,"published":"2009-10-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2008-1818","kev_date_added":null,"published":"2008-04-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands via vulnerable database triggers, potentially compromising data integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2004-1339/"}