Skip to content

Update dependency log4js to v6.4.0 [SECURITY] - #166

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-log4js-vulnerability
Open

Update dependency log4js to v6.4.0 [SECURITY]#166
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-log4js-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Mar 7, 2022

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
log4js (source) 6.1.26.4.0 age confidence

Incorrect Default Permissions in log4js

CVE-2022-21704 / GHSA-82v2-mx6x-wq7q

More information

Details

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:

Severity

  • CVSS Score: 5.5 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

log4js-node/log4js-node (log4js)

v6.4.0

Compare Source

New default file permissions may cause external applications unable to read logs.
A manual code/configuration change is required.

v6.3.0

Compare Source

v6.2.1

Compare Source

v6.2.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 5570265 to 10b14aa Compare March 26, 2022 12:09
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 10b14aa to 92553d3 Compare April 24, 2022 19:38
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 92553d3 to 17b28e8 Compare May 16, 2022 00:32
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 17b28e8 to e339896 Compare June 18, 2022 22:08
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from e339896 to 8580783 Compare September 25, 2022 10:47
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 8580783 to 0d7c47d Compare November 20, 2022 21:02
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 0d7c47d to d8cbbd9 Compare March 18, 2023 00:14
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from d8cbbd9 to cf23bd1 Compare August 10, 2025 12:56
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from cf23bd1 to 70e6708 Compare September 25, 2025 14:35
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 70e6708 to 897dee5 Compare March 5, 2026 18:12
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from 897dee5 to 4aacbff Compare March 13, 2026 14:50
@renovate renovate Bot changed the title Update dependency log4js to v6.4.0 [SECURITY] Update dependency log4js to v6.4.0 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-log4js-vulnerability branch March 27, 2026 00:44
@renovate renovate Bot changed the title Update dependency log4js to v6.4.0 [SECURITY] - autoclosed Update dependency log4js to v6.4.0 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch 2 times, most recently from 4aacbff to 3663e9a Compare March 30, 2026 21:58
@renovate renovate Bot changed the title Update dependency log4js to v6.4.0 [SECURITY] Update dependency log4js to v6.4.0 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title Update dependency log4js to v6.4.0 [SECURITY] - autoclosed Update dependency log4js to v6.4.0 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch 2 times, most recently from 3663e9a to de2315d Compare April 27, 2026 23:50
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from de2315d to fadfd47 Compare July 24, 2026 20:47
@renovate
renovate Bot force-pushed the renovate/npm-log4js-vulnerability branch from fadfd47 to effceff Compare July 30, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants