{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1490 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2006-1490 is a medium-severity vulnerability in Php Php, published on 29 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-1490 and fix it if it is affected.\n\nWhat it is: CVE-2006-1490 is a medium-severity vulnerability in Php Php, published on 29 Mar 2006. 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-2006-1490 exists.\n\nAffected product: Php Php. 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-2006-1490/ (Markdown: https://insights.sbomify.com/CVE-2006-1490/index.md)","id":"CVE-2006-1490","markdown":"https://insights.sbomify.com/CVE-2006-1490/index.md","name":"CVE-2006-1490","record":{"aliases":["GHSA-fc4p-x25r-c4jr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP scripting language","requires_auth":"none","summary":"Remote attackers can read sensitive memory contents by sending crafted binary data to scripts using the html_entity_decode function.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"php","vendor":"php"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"PHP before 5.1.3-RC1 might allow remote attackers to obtain portions of memory via crafted binary data sent to a script that processes user input in the html_entity_decode function and sends the encoded results back to the client, aka a \"binary safety\" issue.  NOTE: this issue has been referred to as a \"memory leak,\" but it is an information leak that discloses memory contents.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-03-29","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-03-29","kind":"exploitdb","ref":"27508","stars":null,"title":"PHP 4.x/5.x - 'Html_Entity_Decode()' Information Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2006-1490","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"php:php","products":["php:php"],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":32,"next":{"headline":"Code injection in n/a","id":"CVE-2006-1491"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-1489"},"products":["n/a"],"published":"2006-03-29","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2012-2688","kev_date_added":null,"published":"2012-07-20"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2376","kev_date_added":null,"published":"2012-05-21"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2011-3268","kev_date_added":null,"published":"2011-08-25"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-4143","kev_date_added":null,"published":"2009-12-21"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-5557","kev_date_added":null,"published":"2008-12-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-2050","kev_date_added":null,"published":"2008-05-05"},{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2008-2051","kev_date_added":null,"published":"2008-05-05"}],"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)"},{"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 read sensitive memory contents by sending crafted binary data to scripts using the html_entity_decode function.","url":"https://insights.sbomify.com/CVE-2006-1490/"}