{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-2611 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-2611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-2611 is a medium-severity vulnerability in n/a, published on 4 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-2611 and fix it if it is affected.\n\nWhat it is: CVE-2004-2611 is a medium-severity vulnerability in n/a, published on 4 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2004-2611 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-2004-2611/ (Markdown: https://insights.sbomify.com/CVE-2004-2611/index.md)","id":"CVE-2004-2611","markdown":"https://insights.sbomify.com/CVE-2004-2611/index.md","name":"CVE-2004-2611","record":{"aliases":["GHSA-rhg2-2jf9-5p9w"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Sophster mail server","requires_auth":"low_privilege","summary":"Attackers can gain privileges because the Change Permissions function incorrectly removes setuid, setgid, and sticky bits during file changes.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sophster","vendor":"steven_schaefer"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The Change Permissions function in the Sophster suite before 0.9.6 28 May 2004 (aka 0.9.6-r5), possibly including Sophster, FreeSophster, and FreeSophsterPAM, removes the (1) setuid, (2) setgid, and (3) sticky bits when changing a file, which might allow attackers to gain privileges or conduct other unauthorized activities.","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":"Privilege escalation in n/a","id":"CVE-2004-2611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2004"},"n_packages":0,"n_references":4,"next":{"headline":"Auth bypass in n/a","id":"CVE-2004-2612"},"packages":[],"prev":{"headline":"mntd_mount.c in mntd before 0.4.2 might allow local users to gain privileges via shell metacharacters in a remount option in the configuration file.","id":"CVE-2004-2610"},"products":["n/a"],"published":"2005-12-04","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-08","vendors":["n/a"]},"summary":"Attackers can gain privileges because the Change Permissions function incorrectly removes setuid, setgid, and sticky bits during file changes.","url":"https://insights.sbomify.com/CVE-2004-2611/"}