CVE-2021-45851: Server-Side Request Forgery in FUXA

@frangoteam/fuxa Updated 02 Oct 2025

Summary

17/03/2022
No i
High
7.5

CVE-2021-45851: Server-Side Request Forgery in FUXA. Affects @frangoteam/fuxa versions < 1.1.3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

FUXA is an npm package developed by the FrangoTeam. It is a server-side application that provides functionality for managing and controlling industrial automation systems. FUXA is vulnerable to a Server-Side Request Forgery (SSRF) attack, which allows an attacker to manipulate the server into making requests to arbitrary destinations. This can lead to the disclosure of sensitive information from the server's internal environment and services, and potentially enable the execution of malicious commands on the server.

Vulnerability Detail

The SSRF vulnerability in FUXA arises from a failure to properly validate user-supplied input. By crafting a malicious request, an attacker can trick the server into making requests to internal resources or external systems. This can result in the disclosure of sensitive information, such as credentials or internal IP addresses, and potentially enable further attacks against the server or other systems. The vulnerability has a CVSS score of 7.5, indicating a high severity level.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If updating to the latest version is not immediately feasible, a temporary workaround can be implemented by implementing server-side input validation and whitelisting of allowed destinations for requests. This can help prevent the exploitation of the SSRF vulnerability by restricting the server's ability to make requests to unauthorized or potentially malicious destinations. Here is an example of how to implement input validation and whitelisting in Node.js:

const allowedDestinations = ['example.com', 'api.example.com'];

function validateRequest(url) {
  const parsedUrl = new URL(url);
  if (allowedDestinations.includes(parsedUrl.hostname)) {
    // Process the request
  } else {
    // Handle unauthorized destination
  }
}

Conclusion

The SSRF vulnerability in FUXA (CVE-2021-45851) poses a significant risk to the security of industrial automation systems. It allows an attacker to manipulate the server into making requests to arbitrary destinations, potentially leading to the disclosure of sensitive information and the execution of malicious commands. To mitigate this vulnerability, it is crucial to update to the latest version of FUXA (1.1.4 or later) and implement proper input validation and whitelisting techniques. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @frangoteam/fuxa →

Share this vulnerability

FAQ

A Server-Side Request Forgery (SSRF) attack is a type of vulnerability that allows an attacker to manipulate a server into making requests to arbitrary destinations. By exploiting this vulnerability, an attacker can potentially access sensitive information from the server's internal environment and services, and execute commands on the server.

An SSRF vulnerability can lead to the disclosure of sensitive information, such as credentials or internal IP addresses. It can also enable an attacker to perform further attacks against the server or other systems, potentially leading to data breaches, unauthorized access, or service disruptions.

To protect your application from SSRF attacks, it is important to implement proper input validation and sanitization techniques. Ensure that user-supplied input is properly validated and restrict the server's ability to make requests to unauthorized or potentially malicious destinations. Additionally, keeping your application and dependencies up to date with the latest security patches is crucial.

Yes, the FUXA development team has addressed the SSRF vulnerability in the latest version (1.1.4) of the package. They have implemented proper input validation and sanitization techniques to mitigate the vulnerability. It is recommended to update to the latest version to ensure the security of your application.

You can find more information about the SSRF vulnerability in FUXA, including the technical details and the steps taken to address the vulnerability, in the GitHub advisory database. The advisory for this vulnerability can be found at: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/03/GHSA-9vp3-7qwq-83r9/GHSA-9vp3-7qwq-83r9.json

Related vulnerabilities

Recent vulnerabilities recorded for @frangoteam/fuxa.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback