{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-2610 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-2610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-2610 is a medium-severity vulnerability in n/a, published on 4 Dec 2005."},"fix_prompt":"Check this codebase for CVE-2004-2610 and fix it if it is affected.\n\nWhat it is: CVE-2004-2610 is a medium-severity vulnerability in n/a, published on 4 Dec 2005. \nExploitation: There is no known exploitation of CVE-2004-2610 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-2610/ (Markdown: https://insights.sbomify.com/CVE-2004-2610/index.md)","id":"CVE-2004-2610","markdown":"https://insights.sbomify.com/CVE-2004-2610/index.md","name":"CVE-2004-2610","record":{"aliases":["GHSA-rwg3-w9r2-cx93"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"mntd","vendor":"stefan_bambach"}],"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":"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.  NOTE: It is not clear whether this is a vulnerability because there is not necessarily any common usage in which privilege boundaries are crossed.  Typical usage would restrict write access to the configuration file.","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":"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","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2004"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2004-2611"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2004-2609"},"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":null,"url":"https://insights.sbomify.com/CVE-2004-2610/"}