CVE-2023-38487 Vulnerability Analysis & Exploit Details

CVE-2023-38487
Vulnerability Scoring

6.5
/10
High Risk

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

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-2023-38487 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:13 UTC
Originally published on: 🕓 04 Aug 2023, 16:15 UTC

Time between publication and last update: 474 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:N/S:U/C:N/I:H/A:L

CVE-2023-38487 Vulnerability Summary

CVE-2023-38487: HedgeDoc is software for creating real-time collaborative markdown notes. Prior to version 1.9.9, the API of HedgeDoc 1 can be used to create notes with an alias matching the ID of existing notes. The affected existing note can then not be accessed anymore and is effectively hidden by the new one. When the freeURL feature is enabled (by setting the `allowFreeURL` config option or the `CMD_ALLOW_FREEURL` environment variable to `true`), any user with the appropriate permissions can create a note by making a POST request to the `/new/<ALIAS>` API endpoint. The `<ALIAS>` parameter can be set to the ID of an existing note. HedgeDoc did not verify whether the provided `<ALIAS>` value corresponds to a valid ID of an existing note and always allowed creation of the new note. When a visitor tried to access the existing note, HedgeDoc will first search for a note with a matching alias before it searches using the ID, therefore only the new note can be accessed. Depending on the permission settings of the HedgeDoc instance, the issue can be exploited only by logged-in users or by all (including non-logged-in) users. The exploit requires knowledge of the ID of the target note. Attackers could use this issue to present a manipulated copy of the original note to the user, e.g. by replacing the links with malicious ones. Attackers can also use this issue to prevent access to the original note, causing a denial of service. No data is lost, as the original content of the affected notes is still present in the database. This issue was fixed in version 1.9.9. As a workaround, disabling freeURL mode prevents the exploitation of this issue. The impact can be limited by restricting freeURL note creation to trusted, logged-in users by enabling `requireFreeURLAuthentication`/`CMD_REQUIRE_FREEURL_AUTHENTICATION`.

Assessing the Risk of CVE-2023-38487

Access Complexity Graph

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

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

  • Confidentiality: None
    CVE-2023-38487 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2023-38487 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: Low
    CVE-2023-38487 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.088% (probability of exploit)

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

CVE-2023-38487 References

External References

CWE Common Weakness Enumeration

CWE-289

Vulnerable Configurations

  • cpe:2.3:a:hedgedoc:hedgedoc:-:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:-:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:0.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:0.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.7.0:-:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.7.0:-:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.7.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.7.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.8.0:-:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.8.0:-:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.8.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.8.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:hedgedoc:hedgedoc:1.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:hedgedoc:hedgedoc:1.9.3:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-38487: 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-46328 – snowflake-connector-nodejs is a NodeJS driver for Snowflake. Versions starting from 1.10.0 to before 2.0.4, are vulnerable to a Time-of-Check to Ti...
  • CVE-2025-46327 – gosnowflake is the Snowflake Golang driver. Versions starting from 1.7.0 to before 1.13.3, are vulnerable to a Time-of-Check to Time-of-Use (TOCTOU...
  • CVE-2025-46326 – snowflake-connector-net is the Snowflake Connector for .NET. Versions starting from 2.1.2 to before 4.4.1, are vulnerable to a Time-of-Check to Tim...
  • CVE-2025-4039 – A vulnerability was found in PHPGurukul Rail Pass Management System 1.0. It has been rated as critical. Affected by this issue is some unknown func...
  • CVE-2025-4038 – A vulnerability was found in code-projects Train Ticket Reservation System 1.0. It has been declared as critical. Affected by this vulnerability is...