turkdevops / grafana

The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB & Prometheus & More
https://grafana.com
Apache License 2.0
1 stars 0 forks source link

CVE-2022-21704 (Medium) detected in log4js-1.1.1.tgz - autoclosed #588

Closed mend-bolt-for-github[bot] closed 2 years ago

mend-bolt-for-github[bot] commented 2 years ago

CVE-2022-21704 - Medium Severity Vulnerability

Vulnerable Library - log4js-1.1.1.tgz

Port of Log4js to work with node.

Library home page: https://registry.npmjs.org/log4js/-/log4js-1.1.1.tgz

Dependency Hierarchy: - @grafana/e2e-6.7.0-pre.tgz (Root Library) - blink-diff-1.0.13.tgz - preceptor-core-0.10.1.tgz - :x: **log4js-1.1.1.tgz** (Vulnerable Library)

Found in HEAD commit: 3b956fc649fb80f3c2734d2976b6fce921c134b7

Found in base branch: datasource-meta

Vulnerability Details

log4js-node is a port of log4js to node.js. In affected versions 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. Users are advised to update.

Publish Date: 2022-01-19

URL: CVE-2022-21704

CVSS 3 Score Details (5.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/log4js-node/log4js-node/security/advisories/GHSA-82v2-mx6x-wq7q

Release Date: 2022-01-19

Fix Resolution: log4js - 6.4.0


Step up your Open Source Security Game with WhiteSource here

mend-bolt-for-github[bot] commented 2 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #599