CVE-2023-31716: @frangoteam/fuxa FUXA Vulnerable To Local File Vulnerability

HIGH
Advisory Identifier: GHSA-45c3-c4c3-8rqg
CVSS 7.5
CWE-98
Published
Advisory Summary

CVE-2023-31716 is a HIGH (CVSS 7.5) fuxa vulnerable to local file vulnerability (CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')) affecting @frangoteam/fuxa libraries in the npm ecosystem. The issue involves fuxa vulnerable to local file inclusion. Remediation is available in the latest vendor maintenance releases.

CVE-2023-31716 at a Glance

CVE Identifier CVE-2023-31716
GHSA Identifier GHSA-45c3-c4c3-8rqg
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Affected Product @frangoteam/fuxa
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2023-31716

To remediate this vulnerability, upgrade all affected @frangoteam/fuxa dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@frangoteam/fuxa fixed: Latest secure release
npm install @frangoteam/fuxa@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @frangoteam/fuxa

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2023-31716, inspect your project dependencies using npm:

npm ls @frangoteam/fuxa

Analyze the terminal output to locate any version of @frangoteam/fuxa in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls @frangoteam/fuxa command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion'), where the php application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. In @frangoteam/fuxa, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

FUXA <= 1.1.12 has a Local File Inclusion vulnerability via file=fuxa.log

CVE-2023-31716 Affected @frangoteam/fuxa Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
@frangoteam/fuxa
npm
≤ 1.1.12

References

Frequently Asked Questions

What is CVE-2023-31716?
CVE-2023-31716 is a security vulnerability in @frangoteam/fuxa involving FUXA vulnerable to Local File Inclusion under CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion').
Which @frangoteam/fuxa versions are affected?
Affected versions include releases prior to current release patches across affected packages: @frangoteam/fuxa.
What version fixes CVE-2023-31716?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is @frangoteam/fuxa affected?
Yes, @frangoteam/fuxa is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2023-31716?
CVE-2023-31716 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2023-31716?
CVE-2023-31716 is classified under CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') (The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.).
How can I check npm dependencies for CVE-2023-31716?
Run the dependency tree command: 'npm ls @frangoteam/fuxa'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-45c3-c4c3-8rqg",
  "modified" : "2024-09-25T17:57:41Z",
  "published" : "2023-09-22T00:30:29Z",
  "aliases" : [ "CVE-2023-31716" ],
  "summary" : "FUXA vulnerable to Local File Inclusion",
  "details" : "FUXA <= 1.1.12 has a Local File Inclusion vulnerability via file=fuxa.log",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@frangoteam/fuxa"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.1.12"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-31716"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/MateusTesser/CVE-2023-31716"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/frangoteam/FUXA"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-98" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-09-22T17:08:32Z",
    "nvd_published_at" : "2023-09-22T00:15:09Z"
  }
}