What is the severity of CVE-2017-15012?

CVE-2017-15012 is rated as a high-severity vulnerability due to its potential for unauthorized file access.

How do I fix CVE-2017-15012?

To fix CVE-2017-15012, ensure that you update OpenText Documentum Content Server to a version newer than 7.3 that addresses this vulnerability.

What types of attacks can occur due to CVE-2017-15012?

CVE-2017-15012 can be exploited to hijack arbitrary files from the Content Server filesystem, which may lead to unauthorized data access.

Who is affected by CVE-2017-15012?

CVE-2017-15012 affects all users of OpenText Documentum Content Server versions up to and including 7.3.

What is the main cause of CVE-2017-15012?

The main cause of CVE-2017-15012 is the lack of proper input validation in the PUT_FILE RPC-command.

Vulnerability/
CVE-2017-15012

high

8.8

CWE

13/10/2017

3/11/2017

CVE-2017-15012: Input Validation

First published: Fri Oct 13 2017(Updated: )

OpenText Documentum Content Server (formerly EMC Documentum Content Server) through 7.3 does not properly validate the input of the PUT_FILE RPC-command, which allows any authenticated user to hijack an arbitrary file from the Content Server filesystem; because some files on the Content Server filesystem are security-sensitive, this leads to privilege escalation.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
OpenText Documentum Content Server	<=7.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-15012?
CVE-2017-15012 is rated as a high-severity vulnerability due to its potential for unauthorized file access.
How do I fix CVE-2017-15012?
To fix CVE-2017-15012, ensure that you update OpenText Documentum Content Server to a version newer than 7.3 that addresses this vulnerability.
What types of attacks can occur due to CVE-2017-15012?
CVE-2017-15012 can be exploited to hijack arbitrary files from the Content Server filesystem, which may lead to unauthorized data access.
Who is affected by CVE-2017-15012?
CVE-2017-15012 affects all users of OpenText Documentum Content Server versions up to and including 7.3.
What is the main cause of CVE-2017-15012?
The main cause of CVE-2017-15012 is the lack of proper input validation in the PUT_FILE RPC-command.

agent/author
agent/description
agent/event
agent/first-publish-date
agent/last-modified-date
agent/references
agent/severity
agent/softwarecombine
agent/tags
agent/type
agent/weakness
collector/nvd-index
vendor/opentext
canonical/opentext documentum content server
version/opentext documentum content server/7.3

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-15012?
CVE-2017-15012 is rated as a high-severity vulnerability due to its potential for unauthorized file access.
How do I fix CVE-2017-15012?
To fix CVE-2017-15012, ensure that you update OpenText Documentum Content Server to a version newer than 7.3 that addresses this vulnerability.
What types of attacks can occur due to CVE-2017-15012?
CVE-2017-15012 can be exploited to hijack arbitrary files from the Content Server filesystem, which may lead to unauthorized data access.
Who is affected by CVE-2017-15012?
CVE-2017-15012 affects all users of OpenText Documentum Content Server versions up to and including 7.3.
What is the main cause of CVE-2017-15012?
The main cause of CVE-2017-15012 is the lack of proper input validation in the PUT_FILE RPC-command.