{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2006-0803 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-0803 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0803 is a medium-severity vulnerability in Suse Suse Linux, published on 23 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-0803 and fix it if it is affected.\n\nWhat it is: CVE-2006-0803 is a medium-severity vulnerability in Suse Suse Linux, published on 23 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-0803 in the wild and no public exploit code.\n\nAffected product: Suse Suse Linux. 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-0803/ (Markdown: https://insights.sbomify.com/CVE-2006-0803/index.md)","id":"CVE-2006-0803","markdown":"https://insights.sbomify.com/CVE-2006-0803/index.md","name":"CVE-2006-0803","record":{"aliases":["GHSA-5fg2-37rc-xj2q"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SUSE YaST Online Update","requires_auth":"none","summary":"Attackers can bypass signature verification in YaST Online Update to install malicious scripts, requiring a patch to restore integrity checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"suse_linux","vendor":"novell"},{"product":"suse_linux","vendor":"suse"}],"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":"The signature verification functionality in the YaST Online Update (YOU) script handling relies on a gpg feature that is not intended for signature verification, which prevents YOU from detecting malicious scripts or code that do not pass the signature check when gpg 1.4.x is being used.","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":"Security feature bypass in n/a","id":"CVE-2006-0803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"suse:suse_linux","products":["suse:suse_linux"],"type":"security_feature_bypass","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-0804"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-0802"},"products":["n/a"],"published":"2006-02-23","related":[{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2010-3912","kev_date_added":null,"published":"2011-01-12"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2010-3110","kev_date_added":null,"published":"2010-10-12"},{"cvss_score":6.9,"headline":"Path traversal in n/a","id":"CVE-2005-4790","kev_date_added":null,"published":"2006-04-26"},{"cvss_score":5,"headline":"Hardcoded credentials in n/a","id":"CVE-2010-1507","kev_date_added":null,"published":"2010-09-03"},{"cvss_score":4.6,"headline":"Privilege escalation in n/a","id":"CVE-2007-4432","kev_date_added":null,"published":"2007-08-20"},{"cvss_score":4.6,"headline":"Race condition in n/a","id":"CVE-2005-3321","kev_date_added":null,"published":"2005-10-27"}],"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":"Attackers can bypass signature verification in YaST Online Update to install malicious scripts, requiring a patch to restore integrity checks.","url":"https://insights.sbomify.com/CVE-2006-0803/"}