renfei / WinterEE

基于SpringCloud的微服务开发脚手架,包含用户管理、角色管理、组织机构管理、权限管理、CMS内容管理。
https://winteree.renfei.net
Apache License 2.0
4 stars 1 forks source link

CVE-2020-5410 (High) detected in spring-cloud-config-server-2.2.2.RELEASE.jar - autoclosed #144

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

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

CVE-2020-5410 - High Severity Vulnerability

Vulnerable Library - spring-cloud-config-server-2.2.2.RELEASE.jar

spring-cloud-config-server

Library home page: https://projects.spring.io/spring-cloud/

Path to dependency file: WinterEE/WinterEE-Config-Serve/pom.xml

Path to vulnerable library: canner/.m2/repository/org/springframework/cloud/spring-cloud-config-server/2.2.2.RELEASE/spring-cloud-config-server-2.2.2.RELEASE.jar

Dependency Hierarchy: - :x: **spring-cloud-config-server-2.2.2.RELEASE.jar** (Vulnerable Library)

Found in HEAD commit: 9d57f3481f4a0f678edb6631b7924d697b67b48b

Found in base branch: master

Vulnerability Details

Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack.

Publish Date: 2020-06-02

URL: CVE-2020-5410

CVSS 3 Score Details (7.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - 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://tanzu.vmware.com/security/cve-2020-5410

Release Date: 2020-06-02

Fix Resolution: org.springframework.cloud:spring-cloud-config:2.2.3.RELEASE,2.1.9.RELEASE


Step up your Open Source Security Game with WhiteSource here

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

:heavy_check_mark: This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.