CVE-2017-20028 Vulnerability Analysis & Exploit Details

CVE-2017-20028
Vulnerability Scoring

5.6
/10
Significant Risk

Security assessments indicate that CVE-2017-20028 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2017-20028 Details

Status: Modified

Last updated: 🕐 17 Jun 2026, 01:14 UTC
Originally published on: 🕚 09 Jun 2022, 23:15 UTC

Time between publication and last update: 1468 days

CVSS Release: version 3

CVSS3 Source

cna@vuldb.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

CVE-2017-20028 Vulnerability Summary

CVE-2017-20028: A vulnerability was found in HumHub 0.20.1/1.0.0-beta.3. It has been classified as critical. This affects an unknown part. The manipulation leads to privilege escalation. It is possible to initiate the attack remotely. Upgrading to version 1.0.0 is able to address this issue. It is recommended to upgrade the affected component.

Assessing the Risk of CVE-2017-20028

Access Complexity Graph

The exploitability of CVE-2017-20028 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-20028

CVE-2017-20028 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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-20028, 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-20028, 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-20028 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2017-20028 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2017-20028 may slightly degrade system performance without fully affecting service 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.211% (probability of exploit)

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

CVE-2017-20028 References

External References

CWE Common Weakness Enumeration

CWE-269

CAPEC Common Attack Pattern Enumeration and Classification

  • Privilege Abuse CAPEC-122 An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources.
  • Privilege Escalation CAPEC-233 An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform.
  • Restful Privilege Elevation CAPEC-58 An adversary identifies a Rest HTTP (Get, Put, Delete) style permission method allowing them to perform various malicious actions upon server data due to lack of access control mechanisms implemented within the application service accepting HTTP messages.

Vulnerable Configurations

  • cpe:2.3:a:humhub:humhub:0.20.1:*:*:*:*:*:*:*
    cpe:2.3:a:humhub:humhub:0.20.1:*:*:*:*:*:*:*
  • cpe:2.3:a:humhub:humhub:1.0.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:humhub:humhub:1.0.0:beta3:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2017-20028: 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-2026-55957 – Missing Critical Step in Authentication vulnerability in Apache Tomcat when the JNDIRealm was configured to authenticate binds using GSSAPI allowed...
  • CVE-2026-55956 – Improper Authorization vulnerability in Apache Tomcat leads to security constraints specified for the default servlet ignoring any method or method...
  • CVE-2026-55955 – Improper Authentication vulnerability in Apache Tomcat allowed a replay attack against the EncryptionInterceptor in the cluster component. This is...
  • CVE-2026-55276 – Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat meant that special roles and empty authorisation constraints were not i...
  • CVE-2026-53434 – Detection of Error Condition Without Action vulnerability in Apache Tomcat when configuring CRLs for a FFM based connector. This issue affects Apa...