{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-1152 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2005-1152 is a low-severity vulnerability in n/a, published on 25 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-1152 and fix it if it is affected.\n\nWhat it is: CVE-2005-1152 is a low-severity vulnerability in n/a, published on 25 May 2005. 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-2005-1152 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-1152/ (Markdown: https://insights.sbomify.com/CVE-2005-1152/index.md)","id":"CVE-2005-1152","markdown":"https://insights.sbomify.com/CVE-2005-1152/index.md","name":"CVE-2005-1152","record":{"aliases":["GHSA-qx3p-r9h5-8q72"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"POP3 mail server","requires_auth":"none","summary":"qpopper creates files with insecure permissions due to improper umask settings, allowing attackers to read or modify sensitive data.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"debian","cpe":[{"product":"qpopper","vendor":"debian"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"popauth.c in qpopper 4.0.5 and earlier does not properly set the umask, which may cause qpopper to create files with group or world-writable permissions.","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":"Misconfiguration in n/a","id":"CVE-2005-1152","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2005"},"n_packages":0,"n_references":7,"next":{"headline":"Code injection in n/a","id":"CVE-2005-1153"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2005-1151"},"products":["n/a"],"published":"2005-05-25","related":[{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2005-1151","kev_date_added":null,"published":"2005-05-25"}],"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":"qpopper creates files with insecure permissions due to improper umask settings, allowing attackers to read or modify sensitive data.","url":"https://insights.sbomify.com/CVE-2005-1152/"}