CVE-2017-2164 Vulnerability Analysis & Exploit Details

CVE-2017-2164
Vulnerability Scoring

6.1
/10
High Risk

If left unpatched, CVE-2017-2164 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2017-2164 Details

Status: Modified

Last updated: 🕒 21 Nov 2024, 03:23 UTC
Originally published on: 🕕 12 May 2017, 18:29 UTC

Time between publication and last update: 2749 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CVE-2017-2164 Vulnerability Summary

CVE-2017-2164: Cross-site scripting vulnerability in SOY CMS with installer 1.8.12 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Assessing the Risk of CVE-2017-2164

Access Complexity Graph

The exploitability of CVE-2017-2164 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2017-2164

With low attack complexity and no required privileges, CVE-2017-2164 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2017-2164, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2017-2164, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2017-2164 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2017-2164 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2017-2164 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.066% (probability of exploit)

EPSS Percentile: 32.09% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 67.91% of others.

CVE-2017-2164 References

External References

CWE Common Weakness Enumeration

CWE-79

CAPEC Common Attack Pattern Enumeration and Classification

  • XSS Using MIME Type Mismatch CAPEC-209 An adversary creates a file with scripting content but where the specified MIME type of the file is such that scripting is not expected. The adversary tricks the victim into accessing a URL that responds with the script file. Some browsers will detect that the specified MIME type of the file does not match the actual type of its content and will automatically switch to using an interpreter for the real content type. If the browser does not invoke script filters before doing this, the adversary's script may run on the target unsanitized, possibly revealing the victim's cookies or executing arbitrary script in their browser.
  • DOM-Based XSS CAPEC-588 This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is inserted into the client-side HTML being parsed by a web browser. Content served by a vulnerable web application includes script code used to manipulate the Document Object Model (DOM). This script code either does not properly validate input, or does not perform proper output encoding, thus creating an opportunity for an adversary to inject a malicious script launch a XSS attack. A key distinction between other XSS attacks and DOM-based attacks is that in other XSS attacks, the malicious script runs when the vulnerable web page is initially loaded, while a DOM-based attack executes sometime after the page loads. Another distinction of DOM-based attacks is that in some cases, the malicious script is never sent to the vulnerable web server at all. An attack like this is guaranteed to bypass any server-side filtering attempts to protect users.
  • Reflected XSS CAPEC-591 This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is "reflected" off a vulnerable web application and then executed by a victim's browser. The process starts with an adversary delivering a malicious script to a victim and convincing the victim to send the script to the vulnerable web application.
  • Stored XSS CAPEC-592 An adversary utilizes a form of Cross-site Scripting (XSS) where a malicious script is persistently "stored" within the data storage of a vulnerable web application as valid input.
  • Cross-Site Scripting (XSS) CAPEC-63 An adversary embeds malicious scripts in content that will be served to web browsers. The goal of the attack is for the target software, the client-side browser, to execute the script with the users' privilege level. An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute code and scripts. Web browsers, for example, have some simple security controls in place, but if a remote attacker is allowed to execute scripts (through injecting them in to user-generated content like bulletin boards) then these controls may be bypassed. Further, these attacks are very difficult for an end user to detect.
  • AJAX Footprinting CAPEC-85 This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Vulnerable Configurations

  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4b:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4b:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4c:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4c:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4d:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4d:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4e:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.1.4e:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.0a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.0a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.1a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.1a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.2a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.2a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4b:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4b:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4c:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.4c:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.5a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.5a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.7a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.7a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.7b:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.2.7b:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.2a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.2a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.4a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.4a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.5a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.3.5a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0b:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0b:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0:c:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0:c:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0c:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.0c:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.1a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.4.1a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.1a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.1a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.3a:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.3a:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.4:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.6:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.6:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.7:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.7:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.8:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.8:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.9:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.9:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.10:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.10:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.11:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.11:*:*:*:*:*:*:*
  • cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.12:*:*:*:*:*:*:*
    cpe:2.3:a:n-i-agroinformatics:soy_cms:1.8.12:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2017-2164: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...