CVE-2021-21501: Path traversal in ServiceCenter

Summary

01/09/2021
Yes i
High
7.5

CVE-2021-21501: Path traversal in ServiceCenter. Affects github.com/apache/servicecomb-service-center versions < 2.0.0. Fixed in 2.0.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ServiceComb ServiceCenter is a package written in Go that provides service registration and discovery capabilities. It is used to manage microservices in a distributed system. The vulnerability identified as CVE-2021-21501 is a path traversal issue in ServiceCenter versions 1.x.x. This vulnerability allows an attacker to access files outside of the intended directory, potentially leading to unauthorized access or information disclosure.

Vulnerability Detail

The vulnerability arises due to improper configuration in ServiceCenter. By exploiting this vulnerability, an attacker can traverse the directory structure and access files that should be restricted. This can result in the exposure of sensitive information or the execution of arbitrary code. The vulnerability has a CVSS score of 7.5, indicating a high severity level.

How To Fix

Minimum fixed version

2.0.0

This is the first release that contains the fix.

go get github.com/apache/servicecomb-service-center@v2.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. It is advised to upgrade to the fixed version as soon as possible.

Conclusion

The path traversal vulnerability in ServiceCenter can be mitigated by upgrading to version 2.0.0 or later. It is crucial to promptly address this vulnerability to prevent unauthorized access and information disclosure. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for github.com/apache/servicecomb-service-center →

Share this vulnerability

FAQ

ServiceComb ServiceCenter is a Go package used for service registration and discovery in distributed systems.

The vulnerability allows an attacker to access files outside of the intended directory, potentially leading to unauthorized access or information disclosure.

The CVSS score of this vulnerability is 7.5, indicating a high severity level.

To fix this vulnerability, upgrade to ServiceCenter version 2.0.0 or later.

No specific workaround is available. It is recommended to upgrade to the fixed version.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/apache/servicecomb-service-center.

How To Fix

Minimum fixed version

2.0.0

This is the first release that contains the fix.

go get github.com/apache/servicecomb-service-center@v2.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback