{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0297 exists.","fix":"No fix has been published for CVE-2008-0297 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-0297 is a medium-severity vulnerability in n/a, published on 16 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-0297 and fix it if it is affected.\n\nWhat it is: CVE-2008-0297 is a medium-severity vulnerability in n/a, published on 16 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0297 exists.\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-2008-0297/ (Markdown: https://insights.sbomify.com/CVE-2008-0297/index.md)","id":"CVE-2008-0297","markdown":"https://insights.sbomify.com/CVE-2008-0297/index.md","name":"CVE-2008-0297","record":{"aliases":["GHSA-6xw3-vghf-g62f"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PhotoKorn web app","requires_auth":"none","summary":"Remote attackers can obtain database credentials by directly accessing update3.php, exposing sensitive configuration data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"photokorn","vendor":"keil_software"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"PhotoKorn allows remote attackers to obtain database credentials via a direct request to update/update3.php, which includes the credentials in its output.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2008-01-11","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2008-01-11","kind":"exploitdb","ref":"4897","stars":null,"title":"photokron 1.7 - Remote Database Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2008-0297","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2008"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2008-0298"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2008-0296"},"products":["n/a"],"published":"2008-01-16","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can obtain database credentials by directly accessing update3.php, exposing sensitive configuration data.","url":"https://insights.sbomify.com/CVE-2008-0297/"}