ID CVE-2020-16934
Summary An elevation of privilege vulnerability exists in the way that Microsoft Office Click-to-Run (C2R) AppVLP handles certain files, aka 'Microsoft Office Click-to-Run Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2020-16928, CVE-2020-16955.
References
Vulnerable Configurations
  • cpe:2.3:a:microsoft:365_apps:-:*:*:*:enterprise:*:*:*
    cpe:2.3:a:microsoft:365_apps:-:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:microsoft:office:2019:*:*:*:*:-:*:*
    cpe:2.3:a:microsoft:office:2019:*:*:*:*:-:*:*
  • cpe:2.3:a:microsoft:office_2013_click-to-run:-:*:*:*:*:*:*:*
    cpe:2.3:a:microsoft:office_2013_click-to-run:-:*:*:*:*:*:*:*
CVSS
Base: 6.8 (as of 21-10-2020 - 16:55)
Impact:
Exploitability:
CWE CWE-269
CAPEC
  • Privilege Escalation
    An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform.
  • Privilege Abuse
    An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources. If access control mechanisms are absent or misconfigured, a user may be able to access resources that are intended only for higher level users. An adversary may be able to exploit this to utilize a less trusted account to gain information and perform activities reserved for more trusted accounts. This attack differs from privilege escalation and other privilege stealing attacks in that the adversary never actually escalates their privileges but instead is able to use a lesser degree of privilege to access resources that should be (but are not) reserved for higher privilege accounts. Likewise, the adversary does not exploit trust or subvert systems - all control functionality is working as configured but the configuration does not adequately protect sensitive resources at an appropriate level.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
cvss-vector via4 AV:N/AC:M/Au:N/C:P/I:P/A:P
Last major update 21-10-2020 - 16:55
Published 16-10-2020 - 23:15
Last modified 21-10-2020 - 16:55
Back to Top