{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15013 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15013 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15013 is a high-severity vulnerability in n/a, published on 13 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-15013 and fix it if it is affected.\n\nWhat it is: CVE-2017-15013 is a high-severity vulnerability in n/a, published on 13 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-15013 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-2017-15013/ (Markdown: https://insights.sbomify.com/CVE-2017-15013/index.md)","id":"CVE-2017-15013","markdown":"https://insights.sbomify.com/CVE-2017-15013/index.md","name":"CVE-2017-15013","record":{"aliases":["GHSA-hvv7-ccqx-87f7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Documentum Content Server","requires_auth":"low_privilege","summary":"Authenticated users can escalate to superuser privileges by manipulating content objects, requiring immediate patching of 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":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"OpenText Documentum Content Server (formerly EMC Documentum Content Server) through 7.3 contains the following design gap, which allows an authenticated user to gain superuser privileges: Content Server stores information about uploaded files in dmr_content objects, which are queryable and \"editable\" (before release 7.2P02, any authenticated user was able to edit dmr_content objects; now any authenticated user may delete a dmr_content object and then create a new one with the old identifier) by authenticated users; this allows any authenticated user to replace the content of security-sensitive dmr_content objects (for example, dmr_content related to dm_method objects) and gain superuser privileges.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-10-17","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-10-17","kind":"exploitdb","ref":"43004","stars":null,"title":"OpenText Documentum Content Server - 'dmr_content' Privilege Escalation"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2017-15013","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2017-15014"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2017-15012"},"products":["n/a"],"published":"2017-10-13","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":"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"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-31871","kev_date_added":null,"published":"2023-05-18"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated users can escalate to superuser privileges by manipulating content objects, requiring immediate patching of Documentum Content Server.","url":"https://insights.sbomify.com/CVE-2017-15013/"}