VDB
Sign up
MEDIUM4.4

GHSA-x2pg-mjhr-2m5x

Exposure of Sensitive Information to an Unauthorized Actor in semantic-release

Quick fix

GHSA-x2pg-mjhr-2m5x — semantic-release: upgrade to the fixed version with the command below.

npm install semantic-release@19.0.3

Details

### 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/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?_ * https://github.com/semantic-release/semantic-release/releases/tag/v19.0.3 * https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI

### For more information If you have any questions or comments about this advisory: * Open a discussion in [semantic-release discussions](https://github.com/semantic-release/semantic-release/discussions)

Are you affected?

Enter the version of the package you're using.

Affected packages

npm/semantic-release
Introduced in: 17.0.4Fixed in: 19.0.3
Fixnpm install semantic-release@19.0.3

References