{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31871 exists.","fix":"No fix has been published for CVE-2023-31871 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31871 is a high-severity vulnerability in n/a, published on 18 May 2023. 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-2023-31871 and fix it if it is affected.\n\nWhat it is: CVE-2023-31871 is a high-severity vulnerability in n/a, published on 18 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31871 exists.\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-2023-31871/ (Markdown: https://insights.sbomify.com/CVE-2023-31871/index.md)","id":"CVE-2023-31871","markdown":"https://insights.sbomify.com/CVE-2023-31871/index.md","name":"CVE-2023-31871","record":{"aliases":["GHSA-r467-q4j9-32j6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Documentum Content Server","requires_auth":"low_privilege","summary":"A local attacker can bypass security controls in a SUID binary to write arbitrary files as root, achieving privilege escalation on OpenText Documentum Content Server.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"documentum_content_server","vendor":"opentext"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"OpenText Documentum Content Server before 23.2 has a flaw that allows for privilege escalation from a non-privileged Documentum user to root. The software comes prepackaged with a root owned SUID binary dm_secure_writer. The binary has security controls in place preventing creation of a file in a non-owned directory, or as the root user. However, these controls can be carefully bypassed to allow for an arbitrary file write as root.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2023-31871","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2023-31873"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-31868"},"products":["n/a"],"published":"2023-05-18","related":[{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2017-15012","kev_date_added":null,"published":"2017-10-13"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-15013","kev_date_added":null,"published":"2017-10-13"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2017-15276","kev_date_added":null,"published":"2017-10-13"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2017-7221","kev_date_added":null,"published":"2017-04-25"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-7220","kev_date_added":null,"published":"2017-04-21"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2017-5585","kev_date_added":null,"published":"2017-02-22"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-22","vendors":["n/a"]},"summary":"A local attacker can bypass security controls in a SUID binary to write arbitrary files as root, achieving privilege escalation on OpenText Documentum Content Server.","url":"https://insights.sbomify.com/CVE-2023-31871/"}