Status: Analyzed
Last modified: 22-06-2023
Published: 08-06-2023

SUMMARY CVE-2023-34238

Gatsby is a free and open source framework based on React. The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the `__file-code-frame` and `__original-stack-frame` paths, exposed when running the Gatsby develop server (`gatsby develop`). Any file in scope of the development server could potentially be exposed. It should be noted that by default `gatsby develop` is only accessible via the localhost ``, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as `--host`, `-H`, or the `GATSBY_HOST=` environment variable. A patch has been introduced in `gatsby@5.9.1` and `gatsby@4.25.7` which mitigates the issue. Users are advised to upgrade. Users unable to upgrade should avoid exposing their development server to the internet.

Access CVSS3 CVE-2023-34238

Attack Complexity Attack Vector Privileges Required Scope User Interaction

Impact CVSS3 CVE-2023-34238

Confidentiality Integrity Availability

Details CVE-2023-34238

EPSS 0.00089
EPSS % 0.38636
  • Path Traversal: An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
  • Using Slashes and URL Encoding Combined to Bypass Validation Logic: This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
  • Manipulating Web Input to File System Calls: An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
  • Using Escaped Slashes in Alternate Encoding: This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • Using Slashes in Alternate Encoding: This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Vulnerable Configurations
  • cpe:2.3:a:gatsbyjs:gatsby:-:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:2.14.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:3.15.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:4.25.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:4.25.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:5.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:5.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:gatsbyjs:gatsby:5.9.0:*:*:*:*:node.js:*:*
CVSS3 Source
CVSS3 Type Primary

ATOM RSS Feed Link for CVE Vulnerabilities

CVE Data Propulsed by AKAOMA CyberSecurity