What security issues are related to CVE-2017-16046?

CVE-2017-16046 was associated with a malware version of the `mariadb` package that previously stole sensitive environmental variables.

What versions of the `mariadb` package are affected by CVE-2017-16046?

CVE-2017-16046 affected versions of the `mariadb` package prior to 1.0.3.

Is CVE-2017-16046 still a threat in the latest `mariadb` package?

No, CVE-2017-16046 is no longer a threat as the package is now owned by MariaDB and is safe to use.

How can I ensure I'm not using a vulnerable version related to CVE-2017-16046?

You can ensure safety by upgrading to the latest version of the `mariadb` package, specifically 1.0.3 or later.

What should I do if I have an affected version of `mariadb` due to CVE-2017-16046?

If you have an affected version, you should immediately upgrade to version 1.0.3 or later to mitigate any risks.

Vulnerability/
CVE-2017-16046

high

7.5

CWE

506

4/6/2018

18/7/2018

16/9/2024

CVE-2017-16046

First published: Mon Jun 04 2018(Updated: )

# Withdrawn Advisory This advisory has been withdrawn because MariaDB now owns https://www.npmjs.com/package/mariadb and the package is no longer malicious. This link is maintained to preserve external references. # Original Description The `mariadb` package is a piece of malware that steals environment variables and sends them to attacker controlled locations. All versions have been unpublished from the npm registry. ## Recommendation As this package is malware, if you find it installed in your environment, the real security concern is determining how it got there. If you have found this installed in your environment, you should: 1. Delete the package 2. Clear your npm cache 3. Ensure it is not present in any other package.json files on your system 4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables. Additionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.

Credit: support@hackerone.com support@hackerone.com

Affected Software	Affected Version	How to fix
npm/mariadb	<=1.0.2
Mariadb Mariadb	=2.13.0
	=2.13.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What security issues are related to CVE-2017-16046?
CVE-2017-16046 was associated with a malware version of the `mariadb` package that previously stole sensitive environmental variables.
What versions of the `mariadb` package are affected by CVE-2017-16046?
CVE-2017-16046 affected versions of the `mariadb` package prior to 1.0.3.
Is CVE-2017-16046 still a threat in the latest `mariadb` package?
No, CVE-2017-16046 is no longer a threat as the package is now owned by MariaDB and is safe to use.
How can I ensure I'm not using a vulnerable version related to CVE-2017-16046?
You can ensure safety by upgrading to the latest version of the `mariadb` package, specifically 1.0.3 or later.
What should I do if I have an affected version of `mariadb` due to CVE-2017-16046?
If you have an affected version, you should immediately upgrade to version 1.0.3 or later to mitigate any risks.

collector/nvd-index
agent/author
agent/type
collector/github-advisory-latest
source/GitHub
alias/GHSA-85fq-56wq-gmcf
alias/CVE-2017-16046
agent/software-canonical-lookup
agent/weakness
agent/severity
agent/softwarecombine
collector/nvd-cve
source/NVD
collector/github-advisory
agent/references
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/trending
agent/tags
agent/source
vendor/mariadb
canonical/mariadb mariadb
version/mariadb mariadb/2.13.0
package-manager/npm

Frequently Asked Questions

What security issues are related to CVE-2017-16046?
CVE-2017-16046 was associated with a malware version of the `mariadb` package that previously stole sensitive environmental variables.
What versions of the `mariadb` package are affected by CVE-2017-16046?
CVE-2017-16046 affected versions of the `mariadb` package prior to 1.0.3.
Is CVE-2017-16046 still a threat in the latest `mariadb` package?
No, CVE-2017-16046 is no longer a threat as the package is now owned by MariaDB and is safe to use.
How can I ensure I'm not using a vulnerable version related to CVE-2017-16046?
You can ensure safety by upgrading to the latest version of the `mariadb` package, specifically 1.0.3 or later.
What should I do if I have an affected version of `mariadb` due to CVE-2017-16046?
If you have an affected version, you should immediately upgrade to version 1.0.3 or later to mitigate any risks.

CVE-2017-16046

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What security issues are related to CVE-2017-16046?

What versions of the `mariadb` package are affected by CVE-2017-16046?

Is CVE-2017-16046 still a threat in the latest `mariadb` package?

How can I ensure I'm not using a vulnerable version related to CVE-2017-16046?

What should I do if I have an affected version of `mariadb` due to CVE-2017-16046?

Company

Resources

Contact

Frequently Asked Questions

What security issues are related to CVE-2017-16046?

What versions of the `mariadb` package are affected by CVE-2017-16046?

Is CVE-2017-16046 still a threat in the latest `mariadb` package?

How can I ensure I'm not using a vulnerable version related to CVE-2017-16046?

What should I do if I have an affected version of `mariadb` due to CVE-2017-16046?