Skip to content

Incorrect Default Permissions in log4js

Moderate severity GitHub Reviewed Published Jan 19, 2022 in log4js-node/log4js-node • Updated Jan 24, 2024

Package

npm log4js (npm)

Affected versions

< 6.4.0

Patched versions

6.4.0

Description

Impact

Default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config.

Patches

Fixed by:

Released to NPM in log4js@6.4.0

Workarounds

Every version of log4js published allows passing the mode parameter to the configuration of file appenders, see the documentation for details.

References

Thanks to ranjit-git for raising the issue, and to @lamweili for fixing the problem.

For more information

If you have any questions or comments about this advisory:

References

@nomiddlename nomiddlename published to log4js-node/log4js-node Jan 19, 2022
Reviewed Jan 19, 2022
Published by the National Vulnerability Database Jan 19, 2022
Published to the GitHub Advisory Database Jan 21, 2022
Last updated Jan 24, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.047%
(19th percentile)

Weaknesses

CVE ID

CVE-2022-21704

GHSA ID

GHSA-82v2-mx6x-wq7q

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.