Also availablein PDF format (533KiB).
Below are useful references to additional CVSS v3.1 documents.
| Resource | Location |
|---|---|
| Specification Document | Includes metric descriptions, formulas, and vector string. Available athttps://www.first.org/cvss/specification-document. |
| User guide | Includes further discussion of CVSS v3.1, a scoring rubric, and a glossary. Available athttps://www.first.org/cvss/user-guide. |
| Examples document | Includes examples of CVSS v3.1 scoring in practice. Available athttps://www.first.org/cvss/examples. |
| CVSS v3.1 calculator | Reference implementation of the CVSS v3.1 equations available athttps://www.first.org/cvss/calculator/3.1. |
| XML schema | Schema definition available athttp://www.first.org/cvss/cvss-v3.1.xsd. |
| CVSS v3.1 main page | Main page for all other CVSS resources:https://www.first.org/cvss. |
This document demonstrates how to apply the CVSS version 3.1 standard to scorespecific vulnerabilities. A summary of each vulnerability is provided, alongwith the attack being scored. CVSS version 2.0 scores are provided to showscoring differences between the two standards. Cases where the CVSS version 3.1metric values differ from their CVSS version 3.0 counterparts are alsodiscussed.
Details of the vulnerabilities and attacks were sourced primarily from theNational Vulnerability Database (NVD) athttps://nvd.nist.gov/vuln.Information from additional sources was also used when more details wererequired.
Important Note: The scoring models assume target systems are employing thevulnerable configuration if applicable.
A vulnerability in the MySQL Server database could allow a remote, authenticateduser to inject SQL code that runs with high privileges on a remote MySQL Serverdatabase. A successful attack could allow any data in the remote MySQL databaseto be read or modified. The vulnerability occurs due to insufficient validationof user-supplied data as it is replicated to remote MySQL Server instances.
An attacker requires an account on the target MySQL database with the privilegeto modify user-supplied identifiers, such as table names. The account must be ona database which is configured to replicate data to one or more remote MySQLdatabases. An attack consists of logging in using the account and modifying anidentifier to a new value that contains a quote character and a fragment ofmalicious SQL. This SQL will later be replicated to, and executed on, one ormore remote systems, as a highly privileged user. The malicious SQL is injectedinto SQL statements in a way that prevents the execution of arbitrary SQLstatements.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | Single |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The attacker connects to the exploitable MySQL database over a network. |
| Attack Complexity | Low | Replication must be enabled on the target database. Following the guidance in Section 2.1.2 of the Specification Document that was added in CVSS v3.1, we assume the system is configured in this way. |
| Privileges Required | Low | The attacker requires an account with the ability to change user-supplied identifiers, such as table names. Basic users do not get this privilege by default, but it is not considered a sufficiently trusted privilege to warrant this metric being High. |
| User Interaction | None | No user interaction is required as replication happens automatically. |
| Scope | Changed | The vulnerable component is the MySQL server database that the attacker logs into to perform the attack. The impacted component is a remote MySQL server database (or databases) that this database replicates to. |
| Confidentiality | Low | The injected SQL runs with high privilege and can access information the attacker should not have access to. Although this runs on a remote database (or databases), it may be possible to exfiltrate the information as part of the SQL statement. The malicious SQL is injected into SQL statements that are part of the replication functionality, preventing the attacker from executing arbitrary SQL statements. |
| Integrity | Low | The injected SQL runs with high privilege and can modify information the attacker should not have access to. The malicious SQL is injected into SQL statements that are part of the replication functionality, preventing the attacker from executing arbitrary SQL statements. |
| Availability | None | Although injected code is run with high privilege, the nature of this attack prevents arbitrary SQL statements being run that could affect the availability of MySQL databases. |
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, usesnondeterministic CBC padding, which makes it easier for man in the middleattackers to obtain plaintext data via a padding-oracle attack, aka the "POODLE"(Padding Oracle on Downgraded Legacy Encryption) issue.
A typical attack scenario is that a victim has visited a web server and theirweb browser now contains a cookie that an attacker wishes to steal. For asuccessful attack, the attacker must be able to modify network traffic betweenthe victim and this web server, and both victim and system must be willing touse SSL 3.0 for encryption.
A typical attack starts by the attacker tricking the victim into visiting a website containing malicious code that then runs on the victim's web browser. SameOrigin Policy (SOP) restrictions in web browsers prevent this code from directlyaccessing the cookie the attacker is trying to steal, but HTTP requests that thecode sends to the web server automatically have the cookie added, and thisbehavior is used in the attack.
The malicious code sends an HTTP request that guesses the value of the firstbyte of the cookie and positions this byte in a specific location. The attackermodifies the encrypted HTTP request such that this byte is used as a paddingvalue. If the server accepts the modified request, the value guessed wascorrect; if not, the code guesses a different value in a new request. Thisprocess is repeated until the entire cookie is disclosed.
Note: The CVSS v3.1 scoring below adheres to the guidelines for ScoringVulnerabilities in Software Libraries from the CVSS v3.1 User Guide. Scoring isbased on the reasonable worst-case implementation scenario, and assumes, forexample, that an SSL library will typically be bound to the network stack(AV:N).
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | None |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The attack is conducted over a network. Note that the attack can take place at any point between the victim and web server over which the network traffic is routed. The value is therefore Network rather than Adjacent Network; the latter is only used for attacks where the attacker must be on the same physical network (or equivalent). |
| Attack Complexity | High | This is a man in the middle attack, and therefore complex for the attacker to perform. |
| Privileges Required | None | An attacker requires no privileges to mount an attack. |
| User Interaction | Required | The victim must be tricked into running malicious code on their web browser. |
| Scope | Unchanged | The vulnerable component is the web server because it insecurely responds to padding errors in a way that can be used to brute force encrypted data. The impacted component is also the web server because the cookie information disclosed is part of its authorization authority. |
| Confidentiality | Low | The attack discloses cookie information that the attacker should not have access to. |
| Integrity | None | |
| Availability | None |
Due to a flaw in the handler function for Remote Procedure Call (RPC) commands,it is possible to manipulate data pointers within the Virtual Machine Executable(VMX) process. This vulnerability may allow a user in a Guest Virtual Machine tocrash the VMX process resulting in a Denial of Service (DoS) on the host orpotentially execute code on the host.
A successful exploit requires an attacker to have access to a Guest VirtualMachine (VM). The Guest VM needs to be configured to have 4GB or more of memory.The attacker would then have to construct a specially crafted remote RPC call toexploit the VMX process.
The VMX process runs in the VMkernel that is responsible for handlinginput/output to devices that are not critical to performance. It is alsoresponsible for communicating with user interfaces, snapshot managers, andremote console. Each virtual machine has its own VMX process which interactswith the host processes via the VMkernel.
The attacker can exploit the vulnerability to crash the VMX process resulting ina DoS of the host or potentially execute code on the host operating system.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | Single |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | VMX process is bound to the network stack and the attacker can send RPC commands remotely. |
| Attack Complexity | Low | The only required condition for this attack is for virtual machines to have 4GB of memory. Virtual machines that have less than 4GB of memory are not affected. |
| Privileges Required | Low | The attacker must have access to the guest virtual machine. This is easy in a tenant environment. |
| User Interaction | None | The attacker requires no user interaction to successfully exploit the vulnerability. RPC commands can be sent anytime. |
| Scope | Changed | The vulnerable component is a VMX process that can only be accessed from the guest virtual machine. The impacted component is the host operating system which has separate authorization authority from the guest virtual machine. |
| Confidentiality | High | Full compromise of the host operating system via remote code execution. |
| Integrity | High | Full compromise of the host operating system via remote code execution. |
| Availability | High | Full compromise of the host operating system via remote code execution. |
Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through6.0.18 permits web applications to replace an XML parser used for other webapplications, which allows local users to read or modify the (1) web.xml, (2)context.xml, or (3) tld files of arbitrary web applications via a craftedapplication that is loaded earlier than the target application.
This Tomcat vulnerability allows a web-apps to reference an XML parser insteadof using the default Apache XML parser. The attacker must remove all existingweb-apps including those in server/webapps, then install a web-app with an XMLparser is stored in WEB-INF/lib. This will cause Tomcat to use the new XMLparser to process all web.xml, context.xml and tld files of other webapps. Ifthat non-standard XML parser is replaced with a malicious one, the content ofthe victim web app XML can be disclosed, the resulting JSP could be corrupted(if it compiled at all) or possibly even weaponized for further attacks.
There are 2 different ways this attack may manifest. First a local privilegeduser could simply replace the non-Apache XML parser with a malicious variant.The second is that an attacker may use social engineering and user interactionto inject the malicious XML parser into the system. We will score for theformer.
| Metric | Value |
|---|---|
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Local | Local user access is required to read/modify Tomcat configuration files. |
| Attack Complexity | Low | No special knowledge is necessary to impact XML parser integrity. |
| Privileges Required | High | The user requires high privileges to be able to modify Tomcat configuration files. |
| User Interaction | None | |
| Scope | Unchanged | Assuming simple webapps that do not maintain separate authorization authority. |
| Confidentiality | Low | Webapp xml and tld files can be exposed. |
| Integrity | Low | The integrity of the XML parser is lost, possibly resulting in a corrupt JSP. |
| Availability | Low | The reasonable outcome behind modifying the XML parser is to make certain web applications unavailable. |
Cisco IOS 12.2 through 12.4 and 15.0 through 15.2 and IOS XE 2.1.x through 2.6.xand 3.1.xS before 3.1.2S, 3.2.xS through 3.4.xS before 3.4.2S, 3.5.xS before3.5.1S, and 3.1.xSG and 3.2.xSG before 3.2.2SG, when AAA authorization isenabled, allow remote authenticated users to bypass intended access restrictionsand execute commands via a (1) HTTP or (2) HTTPS session, aka Bug ID CSCtr91106.
The vulnerability allows an attacker to bypass command authorizationrestrictions assigned to their specific user account and execute commands thatare available to the Roll/Privilege level for which the user is assigned. Forexample, a user that is in a group that is assigned to Privilege level 15(admin) but was restricted to executing a single command via AAA (RADIUS/TACACS)could exploit the vulnerability to execute any other command available to anunrestricted admin user at Privilege level 15.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | Single |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | Attacks are executed via network API. |
| Attack Complexity | Low | No specialized conditions or advanced knowledge is required. |
| Privileges Required | High | While several variants are possible, assume worst-case scenario of captive admin exploiting vulnerability. |
| User Interaction | None | No additional user interaction required for exploit. |
| Scope | Unchanged | The vulnerability allows authorization bypass, but impact is contained to the original scope of vulnerable component. |
| Confidentiality | High | Successful exploitation could result in a complete compromise of the targeted device which results in a complete (High) impact on Confidentiality of the device. |
| Integrity | High | Successful exploitation could result in a complete compromise of the targeted device which results in a complete (High) impact on Integrity of the device. |
| Availability | High | Successful exploitation could result in a complete compromise of the targeted device which results in a complete (High) impact on the Availability of the device. |
iWork in Apple iOS before 8.3 and Apple OS X before 10.10.3 allows remoteattackers to execute arbitrary code or cause a denial of service (memorycorruption) via a crafted iWork file.
A remote user can create a specially crafted iWork file that, when loaded by thetarget user, will trigger a memory corruption error and execute arbitrary code.The attacker must deliver and then convince the local user to open the maliciousiWork file.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Local | The vulnerability is in the local parser. |
| Attack Complexity | Low | Specialized conditions or advanced knowledge is not required. |
| Privileges Required | None | |
| User Interaction | Required | The victim needs to open the malicious iWork file. |
| Scope | Unchanged | |
| Confidentiality | High | Arbitrary code execution. |
| Integrity | High | Arbitrary code execution. |
| Availability | High | Arbitrary code execution. |
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do notproperly handle Heartbeat Extension packets, which allows remote attackers toobtain sensitive information from process memory via crafted packets thattrigger a buffer over-read, as demonstrated by reading private keys, related tod1_both.c and t1_lib.c, aka the Heartbleed bug.
A successful attack requires only sending a specially crafted message to a webserver running OpenSSL. The attacker constructs a malformed “heartbeat request”with a large field length and small payload size. The vulnerable server does notvalidate that the length of the payload against the provided field length andwill return up to 64 kB of server memory to the attacker. It is likely that thismemory was previously utilized by OpenSSL. Data returned may contain sensitiveinformation such as encryption keys or user names and passwords that could beused by the attacker to launch further attacks
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | None |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The vulnerability is in a network service that uses OpenSSL. |
| Attack Complexity | Low | An attacker needs to only find a listening network service to mount an attack. |
| Privileges Required | None | An attacker requires no privileges to mount an attack. |
| User Interaction | None | No user access is required for an attacker to launch a successful attack. |
| Scope | Unchanged | The vulnerable component is OpenSSL which is integrated with the network service, therefore no change in scope occurs during the attack. |
| Confidentiality | High | Access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact to the affected scope (e.g. the attacker can read the administrator's password, or private keys in memory are disclosed to the attacker). |
| Integrity | None | No information can be modified by the attacker. |
| Availability | None | The attacker cannot affect availability through this attack. |
GNU Bash through 4.3 processes trailing strings after function definitions inthe values of environment variables, which allows remote attackers to executearbitrary code via a crafted environment, as demonstrated by vectors involvingthe ForceCommand feature in OpenSSH sshd, the mod_cgi and mod_cgid modules inthe Apache HTTP Server, scripts executed by unspecified DHCP clients, and othersituations in which setting the environment occurs across a privilege boundaryfrom Bash execution, a.k.a. "Shellshock."
A successful attack can be launched by an attacker directly against thevulnerable GNU Bash shell, or in certain cases, by an unauthenticated, remoteattacker through services either written in GNU Bash or services spawning GNUBash shells. In the case of an attack against the Apache HTTP Server runningdynamic content CGI modules, an attacker can submit a request while providingspecially crafted commands as environment variables. These commands will beinterpreted by the handler program, the GNU Bash shell, with the privilege ofthe running HTTPD process. As such, environment variables passed by the attackercould allow installation of software, account enumeration, denial of service,etc. Attacks against other services that have a relationship with the GNU Bashshell are similarly possible.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The reasonable worst-case scenario is a network attack via a web server. |
| Attack Complexity | Low | An attacker needs to only gain access to a listening service that uses the GNU Bash shell as an interpreter or interact with a GNU Bash shell directly. |
| Privileges Required | None | The reasonable worst-case scenario is an attack via a web server which does not require any privileges, e.g., a simple CGI script. |
| User Interaction | None | No user interaction is required for an attacker to launch a successful attack. |
| Scope | Unchanged | Thevulnerable component is the GNU Bash shell which is used as an interpreter for various services or can be accessed directly. It runs within the security authority of the operating system. Theimpacted component is also the operating system, so there is no scope change. |
| Confidentiality | High | An attacker can take complete control of the affected system. |
| Integrity | High | An attacker can take complete control of the affected system. |
| Availability | High | An attacker can take complete control of the affected system. |
The DNS protocol, as implemented in (1) BIND 8 and 9 before 9.5.0-P1, 9.4.2-P1,and 9.3.5-P1; (2) Microsoft DNS in Windows 2000 SP4, XP SP2 and SP3, and Server2003 SP1 and SP2; and other implementations allow remote attackers to spoof DNStraffic via a birthday attack that uses in-bailiwick referrals to conduct cachepoisoning against recursive resolvers, related to insufficient randomness of DNStransaction IDs and source ports, aka "DNS Insufficient Socket EntropyVulnerability" or "the Kaminsky bug."
A successful exploit requires an attacker to identify a recursive nameserverrunning an implementation of DNS that does not supply sufficient randomizationof DNS query/transaction IDs combined with sufficient randomization of sourceports. The attacker then must configure a nameserver to be authoritative for atarget domain and obtain the source port used by the victim recursive nameserver. The attacker then queries the victim recursive nameserver for a namewithin the target domain. Immediately after this request is sent the attackersends a flood of crafted responses to the victim recursive nameserver attemptingto properly guess the query/transaction ID. If the crafted response successfullymatches and arrives prior to a legitimate answer from the actual authoritativesource, the victim recursive nameserver will accept the crafted response and anyinformation within it. This response data will then be stored in the recursiveserver cache and remain there based on the TTL parameters specified by theattacker in the response. All queries matching the target domain sent to thevictim recursive nameserver will then be answered by the poisoned cache andredirect traffic to the attacker’s malicious nameserver and thus direct trafficwhere ever the attacker wishes.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Partial |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The attacker is sending the packets over the network. |
| Attack Complexity | High | The attacker must configure an authoritative source with a public IP to be routed to by the recursive server. The attacker must also beat a race condition to successfully exploit (regardless of how quick that race condition may occur). |
| Privileges Required | None | |
| User Interaction | None | |
| Scope | Changed | The vulnerable component is the DNS server. The impacted component is the victim system who is unknowingly re-directed to unintended network locations based on the malicious DNS answers. |
| Confidentiality | None | Any confidentiality impact is secondary. |
| Integrity | High | The victim user has trusted a poisoned cache and is being directed to any destination the attacker wishes. |
| Availability | None | Any availability impact is secondary. |
Confidentiality, Integrity, and Availability are scored to both vulnerablecomponent and impacted component. However, the impacts are the same.
Sophos Disk Encryption (SDE) 5.x in Sophos Enterprise Console (SEC) 5.x before5.2.2 does not enforce intended authentication requirements for a resume actionfrom sleep mode, which allows physically proximate attackers to obtain desktopaccess by leveraging the absence of a login screen.
When Microsoft Windows systems resume (“wake up”) from sleep or hibernation, thedefault action is to require the user to re-authenticate. When SDE is installed,this functionality becomes disabled, allowing an attacker who has physicalaccess to the system access without credentials by triggering a resume action.
| Metric | Value |
|---|---|
| Access Vector | Local |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Physical | Requires physical access to the device. |
| Attack Complexity | Low | While the attack requires a specific pre-requisite (resume from sleep mode), the attack will succeed every time that pre-requisite occurs, resulting in low complexity. |
| Privileges Required | None | No privileges are required. |
| User Interaction | None | |
| Scope | Unchanged | |
| Confidentiality | High | The attacker has full access to the system with the authority of the logged-in user. We assume the worst-case, an administrative user. |
| Integrity | High | The attacker has full access to the system with the authority of the logged-in user. We assume the worst-case, an administrative user. |
| Availability | High | The attacker has full access to the system with the authority of the logged-in user. We assume the worst-case, an administrative user. Regarding availability impact vs. required control of the device. We are measuring the capabilities granted to the attacker from the vulnerability. |
Directory traversal vulnerability in the ccNewsletter (com_ccnewsletter)component 1.0.5 for Joomla allows remote attackers to read arbitrary files via a.. (dot dot) in the controller parameter in a ccnewsletter action to index.php.
A malicious HTTP request that contains the vulnerable component‘com_ccnewsletter’, and proper series of ‘../’ entries allows an attacker theability to change from the directory where the webserver is installed to anydirectory on the file system of the host OS. Depending on the privileges of theweb application server, an attacker would be able to view the contents of anyfile in the directory searched. Scope is changed due to the ability of thevulnerable component to access the affected system outside of the controllingauthoritative component.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | None |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | |
| Attack Complexity | Low | |
| Privileges Required | None | |
| User Interaction | None | |
| Scope | Changed | It is not clear from the publicly available information if Joomla’s own authorization authority is enabled or plays a role here. For this vulnerability we are assuming that Joomla has its own separate authorization authority and the attacker is able to break out from it and access files on the file system with privileges of web server which has a separate authorization authority. |
| Confidentiality | Low | The attacker is able to read files to which web server has access. |
| Integrity | None | There is no indication that the files can be modified as well. |
| Availability | None | No availability impact. |
The Cisco Carrier Routing System (CRS-X) running IOS XR Software versions 3.9,4.0, and 4.1 allows remote attackers to bypass ACL entries via fragmentedpackets, aka Bug ID CSCtj10975. The vulnerability allows an unauthenticated,remote attacker to bypass device Access Control Entries (ACEs) and send networktraffic that should be denied. It only affects devices that have specific ACEstructures.
Exploitation of this vulnerability can be performed with wide-area networkaccess to the target system and requires the ability to send fragmented IPv4packets to the vulnerable component (router). An attacker can effectively bypassprotocol-based access control for non-initial fragments (fragments with afragment offset not equal to zero), resulting in an integrity impact on thenetwork or devices under the protection of the firewall.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Partial |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The attacker can be multiple hops away from the vulnerable component. |
| Attack Complexity | Low | The complexity of creating packets that match the criteria (non-first fragments) is low. |
| Privileges Required | None | A non-privileged user can initiate the packet stream. |
| User Interaction | None | The attack does not rely on any user interaction. |
| Scope | Changed | The vulnerable component is the CRS itself, while the impacted component is the network and devices protected downstream by the CRS. |
| Confidentiality | None | Impact is scored against the network and devices beyond the firewall (impacted component), and not the CRS (vulnerable component). Any confidentiality loss is a secondary impact. |
| Integrity | Low | Exploitation results in an integrity impact on the network or devices (impacted component) under the protection of the CRS (vulnerable component). |
| Availability | None | Impact is scored against the network and devices beyond the firewall (impacted component), and not the CRS (vulnerable component). Any availability is a secondary impact (for example, targeted DoS attack). |
If Proxy ARP is enabled on an unnumbered interface, an attacker can poison theARP cache and create a bogus forwarding table entry for an IP address,effectively creating a denial of service for that subscriber or interface. WhenProxy ARP is enabled on an unnumbered interface, the router will answer any ARPmessage from any IP address which could lead to exploitable informationdisclosure. This issue can affect any product or platform running Junos OS 10.4,11.4, 11.4X27, 12.1, 12.1X44, 12.1X45, 12.2, 12.3, or 13.1, supportingunnumbered interfaces.
Exploitation of this vulnerability requires network adjacency with the targetsystem and the ability to generate arbitrary ARP replies sent to the connectedinterface. A rogue subscriber can poison the ARP cache and/or create a rogueforwarding table entry for an IP of choice, effectively obscuring that IPaddress or redirecting IP traffic to the attacker.
The resultant impact can be observed as unauthorized modification of a databaseon the vulnerable component, or as an impact on confidentiality or availabilityon attached devices (impacted component). Since the CVSSv3 score for a highconfidentiality (or availability) impact on a changed scope is higher than apartial impact on the vulnerable component, CVSSv3 guidance recommends scoringfor the higher overall impact.
| Metric | Value |
|---|---|
| Access Vector | Adjacent Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Complete |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Adjacent Network | Exploitation of this vulnerability requires network adjacency with the target system. |
| Attack Complexity | Low | The complexity of crafting ARP packets to exploit the vulnerability is low. |
| Privileges Required | None | A non-privileged user can generate the ARP packets. |
| User Interaction | None | The attack does not require any user interaction. |
| Scope | Changed | The vulnerable component is the Junos device itself, while the impacted component is any device for which the ARP entry is poisoned.” |
| Confidentiality | High | The attacker can read any traffic intended for the targeted subscriber(s). |
| Integrity | None | While modification of the routing table on the vulnerable component would represent an impact on integrity, the Integrity impact on the downstream (impacted) component is None. |
| Availability | High | Impact on Availability for the downstream (impacted) component results in a complete denial of service for the targeted subscriber(s). |
Cantemo Portal before 3.2.13, 3.3.x before 3.3.8, and 3.4.x before 3.4.9 has astored cross-site scripting (XSS) vulnerability.
The Cantemo Portal application is affected by a stored XSS vulnerability thatallows low privileged application users to store malicious scripts in theFilename field. These scripts are executed in a victim’s browser when they openthe page containing the vulnerable field.
In the worst case, the victim who inadvertently triggers the attack is a highlyprivileged administrator, so the injected scripts can perform operations on theserver with the privileges of the victim administrator. Such actions includeaccount creation and deletion, deletion of information contained within theportal application, and installation of a remote shell that could lead tofurther compromise.
References:
https://www.bishopfox.com/news/2019/03/cantemo-portal-version-3-8-4-cross-site-scripting/
https://nvd.nist.gov/vuln/detail/CVE-2019-7551
https://blog-posts--cantemo.netlify.com/news/2019/03/cantemo-portal-xss-vulnerabilities/
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | Single |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | A victim must access a vulnerable system via the network. |
| Attack Complexity | Low | The exploit is repeatable without the requirement of system specific reconnaissance or dealing with race conditions. |
| Privileges Required | Low | An attacker must possess some user level privileges to store the malicious scripts in the vulnerable application field. |
| User Interaction | Required | The victim needs to navigate to a web page on the vulnerable server that contains malicious scripts injected by the attacker. |
| Scope | Changed | The vulnerability is in the web server, but the malicious scripts execute in the victim’s browser on their machine. |
| Confidentiality | High | In the worst case, an attacker can create privileged users or perform RCE via shell uploading to take control of the Cantemo Portal application and the underlying operating system. |
| Integrity | High | In the worst case, an attacker can create privileged users or perform RCE via shell uploading to take control of the Cantemo Portal application and the underlying operating system. |
| Availability | High | In the worst case, an attacker can shut down the Cantemo Portal application, or otherwise disrupt service for all users. |
Adobe Acrobat and Reader version 9.0 and earlier are vulnerable to a bufferoverflow, caused by improper bounds checking when parsing a malformed JBIG2image stream embedded within a PDF document. By persuading a victim to open amalicious PDF file, a remote attacker could overflow a buffer and executearbitrary code on the system with the privileges of the victim or cause theapplication to crash.
The vulnerability is exploited by convincing a victim to open a maliciousdocument on a system that uses a vulnerable version of Adobe Acrobat or Reader.An attacker must deliver a malicious document to the victim and relies upon theuser to open it. Then the code execution achieved by the attacker depends on theprivilege level of the user on the system and could potentially result in Highimpacts to Confidentiality, Integrity, and Availability.
References
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0658
http://www.adobe.com/support/security/advisories/apsa09-01.html
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Local | A flaw in the local document software that is triggered by opening a malformed document. |
| Attack Complexity | Low | |
| Privileges Required | None | |
| User Interaction | Required | The victim needs to open the malformed document. |
| Scope | Unchanged | |
| Confidentiality | High | Assuming a worst-case impact of the victim having High privileges on the affected system. |
| Integrity | High | Assuming a worst-case impact of the victim having High privileges on the affected system. |
| Availability | High | Assuming a worst-case impact of the victim having High privileges on the affected system. |
The Bluetooth Stack 2.1 in Microsoft Windows Vista SP1 and SP2 and Windows 7Gold and SP1 does not prevent access to objects in memory that (1) were notproperly initialized or (2) have been deleted, which allows remote attackers toexecute arbitrary code via crafted Bluetooth packets, aka "Bluetooth StackVulnerability."
The vulnerability could allow remote code execution if an attacker sent a seriesof specially crafted Bluetooth packets to an affected system.
This vulnerability only affects systems with Bluetooth capability. The attackerfirst needs to obtain system’s 48-bit Bluetooth address, which is not“discoverable” by default in affected Windows versions. If the system were“discoverable,” it would respond to attacker SDP queries with its Bluetoothaddress. But in the default state, an attacker must obtain your Bluetoothaddress another way – either via bruteforcing it or extracting it from Bluetoothtraffic captured over-the-air. The attacker would need to be in the sameproximity as the target machine in order to send and receive radio transmissionswithin the Bluetooth radio spectrum. Once it is exploited, the attacker can runarbitrary code. The attacker could install programs; view, change, or deletedata; or create new accounts with full user rights.
| Metric | Value |
|---|---|
| Access Vector | Adjacent Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Adjacent Network | The attacker would need to be in the same proximity as the target machine in order to send and receive radio transmissions within the Bluetooth radio spectrum. |
| Attack Complexity | Low | We are assuming that Bluetooth is enabled on the OS. The attacker can obtain system’s 48-bit Bluetooth address by extracting it from Bluetooth traffic captured over-the-air. This attack vector is considered as Low Attack Complexity based on the criteria listed in the specification. |
| Privileges Required | None | An attacker requires no privileges to mount an attack. |
| User Interaction | None | No user interaction is required for this attack. |
| Scope | Unchanged | The vulnerable component and impacted component are the same, which is operating system. |
| Confidentiality | High | The attacker can view, change, or delete data; or create new accounts with full user rights. |
| Integrity | High | The attacker can view, change, or delete data; or create new accounts with full user rights. |
| Availability | High | The attacker can view, change, or delete data; or create new accounts with full user rights. |
The iCloud subsystem in Apple iOS before 7.1 allows physically proximateattackers to bypass an intended password requirement and turn off the Find MyiPhone service or complete a Delete Account action and then associate thisservice with a different Apple ID account, by entering an arbitrary iCloudAccount Password value and a blank iCloud Account Description value.
Find My iPhone helps you locate and protect your iPhone, iPad, iPod touch, orMac if it’s ever lost or stolen. With Find My iPhone set up on your device, youcan do the following:
• Locate your device on a map
• Play a sound on your device to help you find it
• Use Lost Mode to lock and track your device
• Remotely erase all your personal information from the device
Find My iPhone includes a feature called Activation Lock that is designed toprevent anyone else from using your iPhone, iPad, or iPod touch if it's everlost or stolen. Activation Lock is enabled automatically when you turn on FindMy iPhone on a device using iOS 7 or later. Find My iPhone Activation Lock, yourApple ID and password will be required before anyone can:
• Turn off Find My iPhone on your device
• Erase your device
• Reactivate and use your device
This vulnerability allows the attacker to bypass the Activation Lock whenattempting to turn off Find My iPhone. The attacker can turn off Find My iPhonefeature, delete the current iCloud account and associate the device with newiCloud Account without any Apple ID and password of current user.
| Metric | Value |
|---|---|
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Complete |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Physical | The attacker requires physical access to the device |
| Attack Complexity | Low | The attack steps are simple |
| Privileges Required | None | We will consider the worst-case scenario and assume that the device is not protected with a PIN |
| User Interaction | None | No user interaction is required for this attack |
| Scope | Unchanged | The vulnerable and impacted components are the same |
| Confidentiality | None | No direct impact to confidentiality |
| Integrity | High | High due to importance (security) of this feature |
| Availability | None | No direct impact to the availability of the service |
SearchBlox is an enterprise search and data analytics service utilizing ApacheLucene and Elasticsearch.
A cross-site request forgery (CSRF) vulnerability in SearchBlox Server beforeversion 8.2 allows remote attackers to perform actions with the permissions of avictim user, provided the victim user has an active session and is induced totrigger the malicious request.
A specially-crafted URL to the SearchBlox Server containing the appropriateparameter values of an action the attacker wants to perform may be sent to avictim user. This URL may be sent to the victim as part of an HTML document, anemail, or via some other method. If the user interacts with the URL while theuser has an active session on the SearchBlox Server, the URL will send a requestto the server to perform some action with the victim user’s credentials. SinceSearchBlox Server prior to version 8.2 has no request validation mechanism, therequest will be completed if the victim user’s permissions allow such an action.Possible actions include creating or deleting a user account or uploading newSearchBlox configuration settings.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | A victim must access a vulnerable system via the network. |
| Attack Complexity | Low | A phishing email does not absolutely require victim reconnaissance. |
| Privileges Required | None | The attacker does not need any permissions to perform this attack, the attacker lets the victim perform the action on the attacker’s behalf. |
| User Interaction | Required | The victim must click a specially crafted link provided by the attacker. |
| Scope | Unchanged | The vulnerable component is SearchBlox. The impacted component is also SearchBlox as the actions only affect the SearchBlox configuration. |
| Confidentiality | High | The attacker can obtain permissions to view all confidential data contained in SearchBlox. |
| Integrity | High | User accounts can be modified at will as well as SearchBlox configuration. |
| Availability | High | SearchBlox configuration may be modified such as to disable services. |
An attacker using a carefully crafted handshake can force the use of weak keyingmaterial in OpenSSL SSL/TLS clients and servers. This can be exploited by aMan-in-the-middle (MITM) attack where the attacker can decrypt and modifytraffic from the attacked client and server. The attack can only be performedbetween a vulnerable client and server. This is also known as the "CCSInjection" vulnerability, named after the vulnerable ChangeCipherSpec messages.
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does notproperly restrict processing of ChangeCipherSpec messages during the SSL/TLShandshake. A ChangeCipherSpec message tells the client/server to switch fromunencrypted to encrypted communication. If a ChangeCipherSpec message is sent bythe attacker after the connection is initiated but before the master secret hasbeen generated, OpenSSL will generate the keys for the handshake with an emptymaster secret. This zero-length master key allows an attacker to crack theencryption and consequently obtain sensitive information and/or modify SSL/TLStraffic. Note that an attacker requires a man-in-the-middle position with theclient user in order to exploit this attack.
OpenSSL is a library that by itself is not prone to attack. The application thatembeds OpenSSL becomes vulnerable. So, scoring the vulnerability in OpenSSL mustbe done assuming the usage that has the worst consequences. Although someprograms use OpenSSL purely to perform cryptographic operations unrelated tonetworking, e.g., to encrypt/decrypt files stored on disk, the reasonableworst-case scenario where the vulnerability applies is that a program usesOpenSSL to encrypt/decrypt network traffic. The CVSS v3.1 score follows theguidance in User Guide Section 3.7, “Scoring Vulnerabilities in SoftwareLibraries”.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The attacker needs network level access to the communication channel between the client and server. |
| Attack Complexity | High | The attacker must be able to monitor and alter victims' network traffic acting as a man in the middle. Measurable effort is typically required to intercept network traffic in this way and there are uncertainties involved, making attack complexity "High". |
| Privileges Required | None | The attacker doesn’t need any privilege with the client or the server in order to exploit this vulnerability. |
| User Interaction | None | If any human party is involved in the communication, his/her intervention is required. But user interaction is not required for system to system communications. As per “User Guide Section 3.7. Scoring Vulnerabilities in Software Libraries”, the reasonable worst-case usage scenario is considered. |
| Scope | Unchanged | The vulnerable component is OpenSSL. The impacted component is the application using OpenSSL. But OpenSSL, being an embedded library, resides in the security authority of the embedding application. So, the impacts don’t propagate beyond the security authority where the vulnerable component resides. |
| Confidentiality | High | An attacker is able to decrypt and read all SSL/TLS traffic between the client and server. |
| Integrity | High | An attacker is able to decrypt and modify all SSL/TLS traffic between the client and server. |
| Availability | None | There is no impact to availability. |
Following the guidance in “User Guide Section 3.7. Scoring Vulnerabilities inSoftware Libraries”, the above score applies when scoring the vulnerability inthe OpenSSL library itself. If an embedding application is affected by the samevulnerability, it should be scored in the context of the embedding applicationbased on how the vulnerable OpenSSL library is used.
For example, if the embedding application allows human users to only readsensitive information on a communication channel encrypted by the vulnerableOpenSSL library, the score of the vulnerability in the application might beadjusted to 5.3 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N). UI:R as humanintervention is required in the scenario. I:N/A:N as the attacker cannot alterthe data or availability of that vulnerable application embedding OpenSSL.
The Inter-process Communication (IPC) implementation in Google Chrome before22.0.1229.94 allows remote attackers to bypass intended sandbox restrictions andwrite to arbitrary files by leveraging access to a renderer process.
Google Chrome uses a multi-process architecture in which each browser tab mayrun a separate renderer process that communicates with other Chrome processesusing the IPC. By persuading a victim to visit a specially crafted Web site, aremote attacker could exploit this vulnerability to write arbitrary files to theoperating system.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The victim must visit a malicious website that may exist outside the local network. |
| Attack Complexity | Low | The attacker does not need to perform any special reconnaissance for this attack. |
| Privileges Required | None | The attacker does not need any permissions to perform this attack, the attacker lets the victim perform the action on the attacker’s behalf. |
| User Interaction | Required | The victim must click a specially crafted link provided by the attacker. |
| Scope | Changed | Based on the assumption that the attacker is breaking out of Chrome’s controlled sandboxed environment, the vulnerable component is Google Chrome and the impacted component is the operating system on which Chrome is running. |
| Confidentiality | High | The worst-case scenario is Chrome running with administrative privileges. The attacker can overwrite system configuration and grant the attacker access to any data or Administrative privileged access on the system. |
| Integrity | High | The worst-case scenario is Chrome is running with administrative privileges. The attacker can overwrite any file, including important system files. |
| Availability | High | The worst-case scenario is Chrome running with administrative privileges. The attacker can cause a system crash by overwriting specific system files or denying a user access by system reconfiguration. |
This vulnerability allows remote attackers to execute arbitrary code onvulnerable installations of Google Chrome. User interaction is required toexploit this vulnerability in that the victim must visit a malicious page oropen a malicious file.
The specific flaw exists within the handling of JPEG 2000 images. A speciallycrafted JPEG 2000 image embedded inside a PDF can force Google Chrome to writememory past the end of an allocated object. An attacker can leverage thisvulnerability to execute arbitrary code under the context of the currentprocess.
An attacker creates a PDF file embedding a maliciously crafted JPEG 2000 image.This is made available to victims, e.g., via a web page. A victim opens the PDFdocument using a Google Chrome browser, and the browser displays the PDF usingthe built-in PDFium PDF viewer. This triggers the exploit and runs theexecutable code that the attacker placed in the image, taking over the browser.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | Vulnerabilities where the vulnerable component is a separate program invoked from a browser, e.g., a word processor, and which require user interaction to download or receive malicious content which could also be delivered locally, should be scored as Local. For example, a document parsing vulnerability which does not require the network in order to be exploited should be scored as Local, regardless of the method used to distribute such a malicious document (e.g., it could be a link to a web site, or via a USB drive). However, for this vulnerability, a PDF file opened in Google Chrome is automatically displayed using the PDFium functionality that is part of the browser. In such cases where the victim could load a malicious PDF file either via a network or from local media (e.g., a hard disk or USB drive), we score Attack Vector as Network, as this gives the higher Base Score. Vulnerabilities in functionality added to a browser, e.g., libraries, plugins, extensions and add-ons, are treated as part of the browser when determining Attack Vector. For example, a vulnerability in Adobe Flash is scored with an Attack Vector of Network (assuming the victim loads the exploit over a network). |
| Attack Complexity | Low | Specialized access conditions or extenuating circumstances do not exist. |
| Privileges Required | None | An attacker requires no privileges to mount an attack. |
| User Interaction | Required | A successful attack requires a victim to open a malicious PDF file. |
| Scope | Unchanged | The vulnerable component is the victim's Google Chrome web browser. The impacted component is also the victim's Google Chrome browser. |
| Confidentiality | High | The Google Chrome web browser is completely compromised and runs executable code created by the attacker. |
| Integrity | High | The Google Chrome web browser is completely compromised and runs executable code created by the attacker. |
| Availability | High | The Google Chrome web browser is completely compromised and runs executable code created by the attacker. |
The Security Account Manager Remote (SAMR) and Local Security Authority (DomainPolicy) (LSAD) protocols allow access to Windows domains and network shares viathe Server Message Block (SMB) protocol. SAMR/LSAD allow setting an “auth level”which determines how the server authenticates requests. Specifically, setting anauth level of “CONNECT” does not properly sign and authenticate messages. Anattacker with a man-in-the-middle position between a victim user and the remoteSMB server can send a crafted request to downgrade the authentication level ofthe connection to “CONNECT”, allowing the attacker to then impersonate a victim,effectively gaining the privileges of the victim user.
If an attacker maintains a man-in-the-middle position between a victim and aremote SMB server, the attacker can modify requests from the victim to force theSMB server to downgrade its SAMR/LSAD protocols to use an auth level of CONNECT.The attack allows an attacker to access the communication channel used by thevictim and impersonate the victim in transactions due to a lack of properauthentication of messages. Effectively, the user can escalate privileges to theprivilege level of the victim user.
CVE-2016-0128 is the variant for Microsoft Windows and requires the victim userto be a domain administrator attempting an uncommon action, such as a domainjoin, for the attack to succeed. A particular consequence is that the SAMcredentials database may be obtained, allowing further network access.
CVE-2016-2118, meanwhile, is the variant for SAMBA and may affect a more typicaluser performing more common actions such as file or printer sharing.
| Metric | CVE-2016-0128 | CVE-2016-2118 |
|---|---|---|
| Access Vector | Network | Network |
| Access Complexity | Medium | Medium |
| Authentication | None | None |
| Confidentiality Impact | Partial | Partial |
| Integrity Impact | Partial | Partial |
| Availability Impact | None | Partial |
| Metric | CVE-2016-0128 | CVE-2016-2118 | Comments |
|---|---|---|---|
| Attack Vector | Network | Network | This attack is not limited to a collision domain and may be performed against any user on the network for which a man-in-the-middle scenario may be established. |
| Attack Complexity | High | High | The attacker requires specialized access conditions or extenuating circumstances in order to create a man-in-the-middle scenario. In many circumstances this would require access to a private internal network. |
| Privileges Required | None | None | No extra privileges are required to mount an attack. |
| User Interaction | Required | Required | A successful attack requires the victim user to perform a domain join, user account add, printer share, or similar action. The attacker must wait for an action to occur. |
| Scope | Unchanged | Unchanged | For CVE-2016-0128, the vulnerable component is the Windows subsystem consisting of the Windows Domain Controller and associated SAM database, that authenticates the victim’s SMB connections. For CVE-2016-2118, the vulnerable component is the SAMBA server, that authenticates the victim’s SMB connections. For both vulnerabilities, the impacted component is the same as the vulnerable component. |
| Confidentiality | High | High | An attacker can spoof a user and access the victim user’s resources on the vulnerable server. The attacker is assumed to target a highly privileged user. For CVE-2016-0128, a successful attack results in access to all data stored in the SAM. For CVE-2016-2118, although the attacker may not gain access to all data stored in the SAMBA server, it includes data considered to have a direct, serious impact. Confidentiality is therefore High in both cases. |
| Integrity | High | High | An attacker can spoof a user and modify any of the user’s resources on the vulnerable server. The protocol downgrade removes the ability for the server to detect the manipulation. The attacker is assumed to target a highly privileged user. For CVE-2016-0128, a successful attack results in the ability to modify all data stored in the SAM. For CVE-2016-2118, although the attacker may not gain the ability to modify all data stored in the SAMBA server, modification of data considered to have a direct, serious impact is possible. Integrity is therefore High in both cases. |
| Availability | None | High | For CVE-2016-0128, an attacker cannot immediately influence the availability of the service, therefore the Availability is None. For CVE-2016-2118, an attacker can immediately read/write files to a file or printer server, potentially degrading service or even shutting it down, so the impact is High. |
Versions of theWP Mail WordPress plugin before 1.2 are vulnerable to areflected cross-site scripting (XSS) attack. Thereplyto parameter is notsufficiently sanitized, allowing JavaScript to be inserted in the URL.
The attacker creates a link to a WordPress website running a vulnerable versionof the WP Mail plugin. This link contains malicious JavaScript code for thereplyto parameter. The attacker fools a victim into visiting the link, e.g.,by sending the link to the victim in an email or posting the link on a websiteand hoping it will be clicked.
When a victim clicks the link, the vulnerable WordPress server will send thevictim a legitimate web page that has the malicious JavaScript chosen by theattacker. The victim's browser will run the malicious JavaScript in the contextof the vulnerable WordPress website, allowing it to read and modify dataassociated with that site. Reflected XSS attacks typically steal cookiesassociated with the vulnerable website or launch further attacks.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Partial |
| Availability Impact | None |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | The attack can only be exploited over a network. We assume the vulnerable WordPress website is connected to the Internet, as this is a common deployment. |
| Attack Complexity | Low | The attacker can expect repeatable success. |
| Privileges Required | None | The attacker requires no privileges to perform the attack. |
| User Interaction | Required | A victim needs to click the malicious link created by the attacker. |
| Scope | Changed | Thevulnerable component is the vulnerable WordPress web server. Theimpacted component is the victim's browser. |
| Confidentiality | Low | Information in the victim's browser associated with the vulnerable WordPress website can be read by the malicious JavaScript code and sent to the attacker. |
| Integrity | Low | Information in the victim's browser associated with the vulnerable WordPress website can be modified by the malicious JavaScript code. |
| Availability | None | The malicious JavaScript code cannot significantly impact the victim's browser. |
Opera before 57.0.3098.106 is vulnerable to a DLL Search Order hijacking attackwhere an attacker can send a ZIP archive composed of an HTML page along with amalicious DLL to the target. Once the document is opened, it may allow theattacker to take full control of the system from any location within the system.The issue lies in the loading of the shcore.dll and dcomp.dll files: these filesare being searched for by the program in the same system-wide directory wherethe HTML file is executed.
The vulnerability allows an attacker to load a malicious DLL from any locationaccessible by the current user. This means that to exploit this vulnerability,an attacker will not need any special access to the system; instead, an attackercan craft a malicious package and send it across to his target. The target candownload and keep this package anywhere in the system.
Once extracted and any HTML page is executed from this malicious package, due tothe vulnerability, the browser tries to load the DLL files from its currentfolder. Here, the presence of malicious DLL files will trigger the backdoor assoon as the page tries to load in the browser.
The vulnerability is a little different than the conventional DLL hijack becausemost of the DLL hijacks occur from the executable path of the software and arenot system-wide. This means in a conventional scenario the attacker will placemalicious DLL files in the executable folder for the software which wouldtypically be Program Files directory. However, such scenarios would require anattacker to have access to the target machine already. In this particular case,since the DLL files are searched from the current directory from where the HTMLfiles are executed, the attacker will not require local access at all.1
| Metric | Value |
|---|---|
| Access Vector | Local |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Local | Attacker must gain local access, either directly or through social engineering, to load the malicious DLL. |
| Attack Complexity | Low | Attack is repeatable and deterministic. |
| Privileges Required | None | No special privileges are required by the attacker. |
| User Interaction | Required | Victim interaction is required to execute the malicious DLL. |
| Scope | Unchanged | Vulnerable and Impacted Component are the same system. |
| Confidentiality | High | Allows the attacker to take full control of the system |
| Integrity | High | Allows the attacker to take full control of the system |
| Availability | High | Allows the attacker to take full control of the system |
https://blog.lucideus.com/2019/02/opera-search-order-hijacking-cve-2018-18913.html
Versions 8.4.0, 8.5.1, 8.5.2 and 8.5.3 of Oracle Outside in Technology includefilters which perform insufficient validation of their inputs, resulting inunintended behavior.
Oracle Outside in Technology is a library and is not exploitable without aprogram that passes data to it. Section 3.7 of the User Guide provides guidanceon how to score vulnerabilities in libraries and similar software.
The User Guide states that we assume the reasonable worst-case in how thelibrary is likely to be used, score based on this usage and document theseassumptions. The nature of the attack is based on the assumptions we make. Theseare discussed in more detail in theComments column of the CVSS v3.1 tablebelow.
A successful attack may allow an attacker to read all other data accessible tothe library, modify some data accessible to the library, and create partialdenial of service conditions.
In general, we assume the library is used by a program that passes maliciousdata to it without performing further checks.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Network | Although it is possible that this program only accepts input from local processes, the library is commonly used with a web application server which is often deployed on the Internet. We assume the latter as it is the reasonable worst case, i.e. the metric value that results in the greatest Base Score. |
| Attack Complexity | Low | The library can be exploited at will, and we assume the program using the library is the same and does not add any complexity that an attacker needs to overcome to perform a successful attack. |
| Privileges Required | None | We assume the program using the library does not require credentials to be supplied before passing potentially malicious data to it. This is a reasonable worst-case assumption for this library as it is sometimes used on public websites to perform document and image conversions for anonymous users. |
| User Interaction | None | We assume the program using the library does not require the attacker to rely on another user performing an action to perform a successful attack. |
| Scope | Unchanged | We assume the impact of an attack is limited to the library and the program using it. Given the nature of this library it is unlikely it would be used in a way that impacts other components. |
| Confidentiality | High | A successful attack may allow an attacker to read all other data accessible to the library. |
| Integrity | Low | A successful attack may allow an attacker to modify some data accessible to the library. |
| Availability | Low | A successful attack may allow an attacker to create partial denial of service conditions. |
The SmmRuntime BIOS EFI Driver allows local administrators to execute arbitrarycode with System Management Mode (SMM) privileges via unspecified vectors.
Attacker creates a buffer in memory containing exploit code to be executed inSMM context. Attacker then creates a structure with a pointer to the exploitcode’s entry point and triggers an SMI passing a reference to that structure.The SMM driver then calls the exploit code via the supplied function pointer.
| Metric | Value |
|---|---|
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | Single |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Local | The attacker must be able to execute code on the system. |
| Attack Complexity | Low | This attack leverages a failure to verify input parameters in the SmmRuntime driver and can be reproduced consistently with simple code. |
| Privileges Required | High | The attacker must be able to run kernel level (ring 0) code on the target system. |
| User Interaction | None | The vulnerability is built into the BIOS and is always available. There is no user configuration involved. |
| Scope | Changed | Exploiting the vulnerable component grants access to SMM resources that are otherwise protected by hardware and are not accessible from outside SMM. The vulnerable component is not intended to grant unlimited access to this mode of operation. |
| Confidentiality | High | Normally the contents of SMRAM are hidden by hardware from access by kernel level (ring 0) code. This attack allows full disclosure of the precise current contents of SMRAM. |
| Integrity | High | Normally the contents of SMRAM and some specific hardware registers are protected by hardware mechanisms. This exploit grants full access to both SMRAM and any hardware registers that have access restricted to SMM. |
| Availability | High | The attacker can completely control the entire system from SMM and deny access to the system by not returning from SMM. |
Some UEFI BIOS implementations failed to set Flash write protections such as theBIOS_CNTL locking on resume from the S3 suspend to RAM sleep state.
Attacker causes or waits until the system resumes from suspend, and then writesover the current BIOS image in Flash with a new BIOS image modified by theattacker.
| Metric | Value |
|---|---|
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Local | The attacker must be able to execute code on the system. |
| Attack Complexity | Low | The attacker has unfettered access to the Flash part on which the BIOS is stored. |
| Privileges Required | High | The attacker must be able to run kernel level (ring 0) code on the target system, in order to access the Flash part. |
| User Interaction | None | Many affected systems may enter the S3 sleep state on their own in standard configurations after some time has passed without user activity. |
| Scope | Unchanged | There is one component impacted, and that component is responsible for enforcing its own security. |
| Confidentiality | None | The contents of the BIOS Flash part are not read protected and can be read regardless of this vulnerability. |
| Integrity | High | If the BIOS Flash part is not properly protected, the BIOS can be completely overwritten. |
| Availability | High | An attacker can permanently deny service by erasing or corrupting the BIOS and resetting the system. |
Existing UEFI setting restrictions for DCI (Direct Connect Interface) in 5th and6th generation Intel Xeon Processor E3 Family, Intel Xeon Scalable processors,and Intel Xeon Processor D Family allows a limited physical presence attacker topotentially access platform secrets via debug interfaces.
An attacker with physical access can attach a debug device to the DCI interfaceand directly interrogate and control the processor state starting from veryearly in the boot process.
| Metric | Value |
|---|---|
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
| Metric | Value | Comments |
|---|---|---|
| Attack Vector | Physical | The attacker must have physical access to the DCI port in order to attach the debugging device. |
| Attack Complexity | Low | The debugging device is off the shelf hardware that can be purchased from Intel by anybody. |
| Privileges Required | None | The attacker has complete access to the state of the processor, directly bypassing all security protections. |
| User Interaction | None | Affected systems enable DCI support by default in the BIOS setup screen. |
| Scope | Changed | The attacker is granted full access to the state of the machine at a hardware level not normally available to users of the system. All software-based security mechanisms and many hardware-based security mechanisms are fully bypassed. |
| Confidentiality | High | The entire operational state of the target machine is fully exposed. Any secret that enters memory is exposed. |
| Integrity | High | The entire operational state of the target machine may be modified to any state permitted by hardware. |
| Availability | High | An attacker can permanently deny service by multiple means, including but not limited to replacing the operating system and modifying UEFI variables that would normally be inaccessible which govern the boot process. |
A remote code execution vulnerability exists in the way the scripting enginehandles objects in memory in Microsoft browsers. The vulnerability could corruptmemory in such a way that an attacker could execute arbitrary code in thecontext of the current user. An attacker who successfully exploited thevulnerability could gain the same user rights as the current user. If thecurrent user is logged on with administrative user rights, an attacker whosuccessfully exploited the vulnerability could take control of an affectedsystem. An attacker could then install programs; view, change, or delete data;or create new accounts with full user rights.
The security update addresses the vulnerability by modifying how the scriptingengine handles objects in memory.
In a web-based attack scenario, an attacker could host a specially craftedwebsite designed to exploit the vulnerability through a Microsoft browser andthen convince a user to view the website. An attacker could also embed anActiveX control marked "safe for initialization" in an application or MicrosoftOffice document that hosts the browser rendering engine. The attacker could alsotake advantage of compromised websites and websites that accept or hostuser-provided content or advertisements. These websites could contain speciallycrafted content that could exploit the vulnerability.
| Metric | Value |
|---|---|
| Access Vector | Network |
| Access Complexity | High |
| Authentication | None |
| Confidentiality Impact | Complete |
| Integrity Impact | Complete |
| Availability Impact | Complete |
| Metric | IE 11 | Edge | Comments |
|---|---|---|---|
| Attack Vector | Network | Network | The victim must visit a malicious website that may exist outside the local network. |
| Attack Complexity | High | High | The attacker can expect repeatable success. |
| Privileges Required | None | None | The attacker does not need any permissions to perform this attack, the attacker lets the victim perform the action on the attacker's behalf. |
| User Interaction | Required | Required | The victim must click a specially-crafted link provided by the attacker. |
| Scope | Unchanged | Unchanged | The vulnerable component and impacted component are the same, which is operating system. |
| Confidentiality | High | Low | The Internet Explorer sandbox runs at a higher integrity level than Edge and allows sandbox features to be disabled, granting access to local files. Edge restricts access to local resources that are generated when browsing (cookies, temp files, etc.). |
| Integrity | High | Low | Internet Explorer could be configured to allow access to local files, which may include access to important system files. An attacker could overwrite these files. The Edge AppContainer restricts access to system files. |
| Availability | High | None | Internet Explorer could be configured to allow access to local files, which may include access to important system files. An attacker could cause a system crash by overwriting these files. The Edge AppContainer restricts access to system files. |