{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-0631 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-0631 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0631 is a medium-severity vulnerability in n/a, published on 10 Feb 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-0631 and fix it if it is affected.\n\nWhat it is: CVE-2006-0631 is a medium-severity vulnerability in n/a, published on 10 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-0631 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-2006-0631/ (Markdown: https://insights.sbomify.com/CVE-2006-0631/index.md)","id":"CVE-2006-0631","markdown":"https://insights.sbomify.com/CVE-2006-0631/index.md","name":"CVE-2006-0631","record":{"aliases":["GHSA-gwc7-xw2f-f6wx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl mailback script","requires_auth":"none","summary":"Remote attackers can inject CRLF characters into mail headers to use the mailback script as a spam proxy.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mailback","vendor":"erik_c._thauvin"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"CRLF injection vulnerability in mailback.pl in Erik C. Thauvin mailback allows remote attackers to use mailback as a \"spam proxy\" by modifying mail headers, including recipient e-mail addresses, via newline characters in the Subject field.","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":"Other in n/a","id":"CVE-2006-0631","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2006"},"n_packages":0,"n_references":7,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2006-0632"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2006-0630"},"products":["n/a"],"published":"2006-02-10","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":"Remote attackers can inject CRLF characters into mail headers to use the mailback script as a spam proxy.","url":"https://insights.sbomify.com/CVE-2006-0631/"}