CVE-2023-45282: Prototype Pollution in NASA Open MCT

openmct Updated 02 Oct 2025

Summary

06/10/2023
No i
High
7.5

CVE-2023-45282: Prototype Pollution in NASA Open MCT. Affects openmct versions < 3.0.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

NASA Open MCT (aka openmct) is an open-source software framework for building web-based mission control applications. It provides a customizable user interface and a set of APIs for developers to create and manage telemetry displays, historical data views, and other features. However, a vulnerability has been discovered in Open MCT that allows for prototype pollution, which can be exploited through an import action.

Vulnerability Detail

The prototype pollution vulnerability in Open MCT can lead to the modification or addition of properties to existing objects. This can result in unexpected behavior or security issues, such as remote code execution or privilege escalation. The vulnerability arises from improper handling of user-supplied input during the import action, allowing an attacker to inject malicious data that pollutes the prototype chain of objects.

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

As a temporary workaround, developers can disable the import action or implement input validation and sanitization measures to mitigate the risk of prototype pollution. Here is an example of input validation using JavaScript:

function validateImportData(data) {
  if (typeof data === 'object' && !Array.isArray(data)) {
    // Perform additional validation checks
    return true;
  }
  return false;
}

By validating the imported data to ensure it is an object and not an array, the risk of prototype pollution can be reduced.

Conclusion

The prototype pollution vulnerability in NASA Open MCT can have serious security implications. It is crucial to update to the latest version and implement proper input validation to mitigate the risk. For further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for openmct →

Share this vulnerability

FAQ

Prototype pollution is a vulnerability that occurs when an attacker can modify the prototype of an object, leading to unexpected behavior or security issues.

The vulnerability in Open MCT can be exploited through the import action, where user-supplied input is not properly validated, allowing for the pollution of object prototypes.

The prototype pollution vulnerability in Open MCT can result in remote code execution, privilege escalation, or other security issues, depending on how it is exploited.

Yes, updating Open MCT to the latest version, commit 545a177 or later, includes the necessary patches to address the prototype pollution vulnerability.

As a temporary workaround, developers can disable the import action or implement input validation and sanitization measures to reduce the risk of prototype pollution.

Related vulnerabilities

Recent vulnerabilities recorded for openmct.

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