Sensitive Data Exposure in pem
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-200.
Summary
Versions of `pem` before 1.13.2 expose sensitive data when the `readPkcs12` is used. The `readPkcs12` function reads the certificate and key data from a pkcs12 file using the encryption password. As part of this process it creates a globally readable file with a filename of 20 random 0-f characters in the temporary directory containing the password which is then read by OpenSSL. The file containing the password is never cleaned up after it is used giving access to the pkcs12 password to any other users with access to read files from the system. ## Recommendation Update to version 1.13.2 or later.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | pem (npm) | before 1.13.2 | 1.13.2 | Patch available | GHSA-pgcr-7wm4-mcv6 |
- pem (npm) Vendor— Affected before 1.13.2 Fixed in 1.13.2 Patch available GHSA-pgcr-7wm4-mcv6
Remediation
- Fix · GHSA-pgcr-7wm4-mcv6 pem (npm) Fixed in 1.13.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-pgcr-7wm4-mcv6
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences