{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-3627 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2005-3627 is a high-severity memory corruption vulnerability in n/a, published on 6 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-3627 and fix it if it is affected.\n\nWhat it is: CVE-2005-3627 is a high-severity memory corruption vulnerability in n/a, published on 6 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2005-3627 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-3627/ (Markdown: https://insights.sbomify.com/CVE-2005-3627/index.md)","id":"CVE-2005-3627","markdown":"https://insights.sbomify.com/CVE-2005-3627/index.md","name":"CVE-2005-3627","record":{"aliases":["DEBIAN-CVE-2005-3627","GHSA-738f-c7mc-xp78"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PDF rendering library","requires_auth":"none","summary":"Attackers can execute arbitrary code via malicious PDF files due to unchecked values in Xpdf's DCTDecode stream processing.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"xpdf","vendor":"xpdf"}],"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":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Stream.cc in Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allows attackers to modify memory and possibly execute arbitrary code via a DCTDecode stream with (1) a large \"number of components\" value that is not checked by DCTStream::readBaselineSOF or DCTStream::readProgressiveSOF, (2) a large \"Huffman table index\" value that is not checked by DCTStream::readHuffmanTables, and (3) certain uses of the scanInfo.numComps value by DCTStream::readScanInfo.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2005-3627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":86,"next":{"headline":"Memory corruption in n/a","id":"CVE-2005-3628"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2005-3626"},"products":["n/a"],"published":"2006-01-06","related":[{"cvss_score":9.3,"headline":"Integer overflow in n/a","id":"CVE-2007-5392","kev_date_added":null,"published":"2007-11-08"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-5393","kev_date_added":null,"published":"2007-11-08"},{"cvss_score":7.6,"headline":"Memory corruption in n/a","id":"CVE-2007-4352","kev_date_added":null,"published":"2007-11-08"},{"cvss_score":7.6,"headline":"Command injection in n/a","id":"CVE-2000-0727","kev_date_added":null,"published":"2000-10-13"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2006-0746","kev_date_added":null,"published":"2006-03-09"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2006-0301","kev_date_added":null,"published":"2006-01-30"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2005-3628","kev_date_added":null,"published":"2006-01-23"}],"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-07","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via malicious PDF files due to unchecked values in Xpdf's DCTDecode stream processing.","url":"https://insights.sbomify.com/CVE-2005-3627/"}