semantic-release
Affected
- introduced
17.0.4, fixed19.0.3(semver)
Fixed versions
19.0.3
Fix
- Fixed version
19.0.3npm install [email protected]
Advisory
Also known as: CVE-2022-31051
Exposure of Sensitive Information to an Unauthorized Actor in semantic-release
Impact
_What kind of vulnerability is it? Who is impacted?_
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.
Patches
_Has the problem been patched? What versions should users upgrade to?_
Fixed in 19.0.3
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Secrets that do not contain characters that are excluded from encoding with encodeURI when included in a URL are already masked properly.
References
_Are there any links users can visit to find out more?_
For more information
If you have any questions or comments about this advisory:
Medium Basis: The source's own band: MODERATE
17.0.4, fixed 19.0.3 (semver)19.0.3
19.0.3npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0