CVE-2017-16046: Hijacked Environment Variables in mariadb

mariadb Updated 02 Oct 2025

Summary

18/07/2018
HIGH
No i
High
7.5

GHSA-85fq-56wq-gmcf: Withdrawn Advisory: mariadb was malware. Affects mariadb versions < 1.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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The mariadb package is a popular npm package used for interacting with MariaDB databases. It provides a set of functions and utilities to establish connections, execute queries, and manage data in a MariaDB database. However, all versions of the mariadb package have been found to contain a vulnerability that allows environment variables to be hijacked by malware. This malware steals the environment variables and sends them to attacker-controlled locations, potentially compromising sensitive information and credentials.

Vulnerability Detail

The vulnerability in the mariadb package allows an attacker to steal environment variables and exfiltrate them to their own servers. This can lead to unauthorized access to sensitive information, such as database credentials, API keys, and other sensitive data stored in environment variables. The impact of this vulnerability depends on the nature of the compromised environment variables and the systems they grant access to. It is important to identify and mitigate this vulnerability to prevent further exploitation and potential data breaches.

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

There is no specific workaround for this vulnerability. It is crucial to follow the steps mentioned in the 'how_to_fix' section to fully mitigate the issue.

Conclusion

The mariadb package has been found to contain a vulnerability that allows environment variables to be hijacked by malware. It is crucial to take immediate action to remove the package, clear the npm cache, regenerate credentials, and review any exposed services. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for mariadb →

Share this vulnerability

FAQ

The malware in the mariadb package intercepts the environment variables used by the package and sends them to attacker-controlled servers.

Sensitive information stored in environment variables, such as database credentials, API keys, and other credentials, can be compromised.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.

The presence of the mariadb package itself does not indicate compromise. However, if you find it installed in your environment, it is important to investigate how it got there and review other systems and credentials for signs of compromise.

If you find the mariadb package installed in your environment, follow the steps mentioned in the 'how_to_fix' section to remove the package, clear your npm cache, regenerate credentials, and review any exposed services.

Related vulnerabilities

Recent vulnerabilities recorded for mariadb.

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