CVE-2022-31051 Exposure of Sensitive Information to an Unauthorized Actor in semantic-release
Attackers can view sensitive secrets in semantic-release logs if specific characters are present and repository access requires URL credential injection.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-31051?
CVE-2022-31051 is a medium-severity vulnerability in semantic-release, published on 9 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
semantic-release is an open source npm package for automated version management and package publishing. In affected versions secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by `encodeURI`. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials. Users are advised to upgrade. Users unable to upgrade should ensure that secrets that do not contain characters that are excluded from encoding with `encodeURI` when included in a URL are already masked properly.
Weakness: CWE-200
Which versions are affected by CVE-2022-31051?
2 open source packages ship an affected version, including semantic-release. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
semantic-release npm | From 17.0.4 | 19.0.3 |
semantic-release npm | From 17.0.4 | 19.0.3 |
Products include Semantic-Release Project Semantic-Release.
How do I fix CVE-2022-31051?
Upgrade semantic-release to 19.0.3 or later.
Is CVE-2022-31051 being exploited?
There is no known exploitation of CVE-2022-31051 in the wild and no public exploit code.
Other vulnerabilities in semantic-release
Sources
Also known as GHSA-x2pg-mjhr-2m5x.