CVE-2023-47628 Vulnerability Analysis & Exploit Details

CVE-2023-47628
Vulnerability Scoring

4.2
/10
Medium Risk

The vulnerability CVE-2023-47628 could compromise system integrity but typically requires user interaction to be exploited.

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: Required
    User interaction is necessary for successful exploitation.

CVE-2023-47628 Details

Status: Modified

Last updated: 🕣 21 Nov 2024, 08:30 UTC
Originally published on: 🕐 14 Nov 2023, 01:15 UTC

Time between publication and last update: 373 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-47628 Vulnerability Summary

CVE-2023-47628: DataHub is an open-source metadata platform. DataHub Frontend's sessions are configured using Play Framework's default settings for stateless session which do not set an expiration time for a cookie. Due to this, if a session cookie were ever leaked, it would be valid forever. DataHub uses a stateless session cookie that is not invalidated on logout, it is just removed from the browser forcing the user to login again. However, if an attacker extracted a cookie from an authenticated user it would continue to be valid as there is no validation on a time window the session token is valid for due to a combination of the usage of LegacyCookiesModule from Play Framework and using default settings which do not set an expiration time. All DataHub instances prior to the patch that have removed the datahub user, but not the default policies applying to that user are affected. Users are advised to update to version 0.12.1 which addresses the issue. There are no known workarounds for this vulnerability.

Assessing the Risk of CVE-2023-47628

Access Complexity Graph

The exploitability of CVE-2023-47628 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-2023-47628

CVE-2023-47628 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-2023-47628, 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-2023-47628, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2023-47628 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2023-47628 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2023-47628 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.076% (probability of exploit)

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

CVE-2023-47628 References

External References

CWE Common Weakness Enumeration

CWE-613

Vulnerable Configurations

  • cpe:2.3:a:datahub_project:datahub:-:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:-:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.1.0:alpha:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.1.0:alpha:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.1.1:alpha:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.1.1:alpha:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.2.0:alpha:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.2.0:alpha:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.5.0:beta:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.5.0:beta:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.6:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.6:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.7:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.7:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.8:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.8:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.9:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.9:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.10:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.10:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.11:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.11:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.12:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.12:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.13:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.13:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.14:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.14:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.15:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.15:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.16:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.16:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.17:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.17:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.18:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.18:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.19:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.19:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.20:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.20:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.21:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.21:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.22:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.22:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.23:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.23:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.24:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.24:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.25:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.25:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.26:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.26:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.27:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.27:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.28:-:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.28:-:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.28:rc1:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.28:rc1:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.29:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.29:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.30:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.30:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.31:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.31:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.32:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.32:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.33:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.33:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.34:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.34:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.35:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.35:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.36:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.36:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.37:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.37:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.38:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.38:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.39:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.39:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.40:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.40:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.41:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.41:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.42:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.42:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.43:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.43:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.44:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.44:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.8.45:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.8.45:*:*:*:*:*:*:*
  • cpe:2.3:a:datahub_project:datahub:0.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:datahub_project:datahub:0.9.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-47628: 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-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...