CVE-2023-44312: Apache ServiceComb Service-Center Exposure of Sensitive Information to an Unauthorized Actor

Summary

31/01/2024
Yes i
Moderate
5.8

CVE-2023-44312: Exposure of Sensitive Information to an Unauthorized Actor in Apache ServiceComb Service-Center. Affects github.com/apache/servicecomb-service-center versions < 2.2.0. Fixed in 2.2.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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Apache ServiceComb Service-Center is an open-source service registry and discovery component that provides a platform for managing microservices. It is written in Go and is a critical part of the ServiceComb ecosystem. Service-Center allows developers to register, discover, and manage microservices, enabling efficient communication between different services. However, an exposure of sensitive information vulnerability has been identified in versions prior to 2.1.0.

Vulnerability Detail

The vulnerability in Apache ServiceComb Service-Center allows an unauthorized actor to access sensitive information. This could lead to potential data breaches and unauthorized access to critical resources. The vulnerability arises due to a lack of proper access controls and authentication mechanisms. Attackers can exploit this vulnerability to gain unauthorized access to sensitive information, compromising the confidentiality and integrity of the system.

How To Fix

Latest published version: v1.4.8 as of 23 Oct 2026

go get github.com/apache/servicecomb-service-center@v1.4.8

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2.0

This is the first release that contains the fix.

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

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

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version as soon as possible to ensure the security of the system.

Conclusion

The exposure of sensitive information vulnerability in Apache ServiceComb Service-Center can have severe consequences, including data breaches and unauthorized access. It is crucial to upgrade to the fixed version, 2.2.0, or later, to mitigate the risk and ensure the security of the system. For further support on vulnerability remediation, you can reach out to DevNack.com.

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

Share this vulnerability

FAQ

Apache ServiceComb Service-Center is an open-source service registry and discovery component that enables efficient communication between microservices.

This vulnerability allows unauthorized actors to access sensitive information, potentially leading to data breaches and unauthorized access to critical resources.

To fix this vulnerability, it is recommended to upgrade to Apache ServiceComb Service-Center version 2.2.0 or later.

There are no known workarounds for this vulnerability. Upgrading to the fixed version is the recommended solution.

For more information about this vulnerability, you can refer to the Apache ServiceComb Service-Center advisory on the GitHub Advisory Database.

Related vulnerabilities

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Latest published version: v1.4.8 as of 23 Oct 2026

go get github.com/apache/servicecomb-service-center@v1.4.8

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2.0

This is the first release that contains the fix.

go get github.com/apache/servicecomb-service-center@v2.2.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