{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-0463 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-0463 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0463 is a high-severity SQL injection vulnerability in n/a, published on 17 Feb 2005. It can be exploited over the network."},"fix_prompt":"Check this codebase for CVE-2005-0463 and fix it if it is affected.\n\nWhat it is: CVE-2005-0463 is a high-severity SQL injection vulnerability in n/a, published on 17 Feb 2005. It can be exploited over the network.\nExploitation: There is no known exploitation of CVE-2005-0463 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-0463/ (Markdown: https://insights.sbomify.com/CVE-2005-0463/index.md)","id":"CVE-2005-0463","markdown":"https://insights.sbomify.com/CVE-2005-0463/index.md","name":"CVE-2005-0463","record":{"aliases":["GHSA-p6gq-gpv8-rq69"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ulog-php web application","requires_auth":"unknown","summary":"SQL injection vulnerabilities in Ulog-php allow attackers to manipulate database queries, potentially leading to unauthorized data access or modification.","user_interaction":"unknown","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ulog-php","vendor":"inl"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Unknown \"major security flaws\" in Ulog-php before 1.0, related to input validation, have unknown impact and attack vectors, probably related to SQL injection vulnerabilities in (1) host.php, (2) port.php, and (3) index.php.","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-2005-0463","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2005"},"n_packages":0,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-0464"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-0462"},"products":["n/a"],"published":"2005-02-17","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"SQL injection vulnerabilities in Ulog-php allow attackers to manipulate database queries, potentially leading to unauthorized data access or modification.","url":"https://insights.sbomify.com/CVE-2005-0463/"}