ServicecombApplication · Apache
CVE-2021-21501
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper configuration will cause ServiceComb ServiceCenter Directory Traversal problem in ServcieCenter 1.x.x versions and fixed in 2.0.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceServiceComb ServiceCenter versions 1.x.x contain a directory traversal vulnerability caused by improper configuration. Attackers can exploit this to access files outside the web root directory through specially crafted path requests. The vulnerability is exploitable over the network without authentication, consistent with its CVSS 7.5 rating.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ServicecombApplication
>= 1.0.0, < 2.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ServiceCenter versionCheck the installed version of Apache ServiceComb ServiceCenter. This is typically visible in the startup logs, the WAR/JAR file name, or by querying the /v4/metadata endpoint if exposed. Compare this version against the affected range: >= 1.0.0 and < 2.0.0.Affected if The installed version falls within 1.0.0 through 1.x.x (anything less than 2.0.0).
-
Verify network exposure of ServiceCenter APIDetermine if the ServiceCenter REST API port (default 30100) or web interface is accessible from untrusted networks. Check firewall rules, reverse proxy configurations, or cloud security groups allowing inbound access to ServiceCenter ports.Affected if The ServiceCenter API or web console is exposed to untrusted/network-accessible interfaces without proper network segmentation.
-
Inspect file serving configurationReview ServiceCenter configuration files (typically in the conf/ directory) for settings related to static file serving, path validation, or web resource handling. Look for any configurations that allow arbitrary file path traversal in API requests.Affected if Configuration permits unrestricted path parameters in API requests or lacks input validation on file path parameters.
-
Test for directory traversal vulnerabilitySend a crafted HTTP request using path traversal sequences (such as /..%2F..%2F) to accessible API endpoints. If the response returns file content from outside the intended web root directory, the vulnerability is present.Affected if Requests with traversal sequences successfully return files from outside the web root directory.
You are affected if ServiceCenter version is 1.x.x (below 2.0.0) AND the API is network-accessible AND the configuration lacks proper path validation to prevent directory traversal attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.0
Upgrade ServiceCenter to version 2.0.0 or later. Review and harden configuration settings to prevent directory traversal, ensuring input validation on file path parameters and restricting access to sensitive directories.
2.0.0
- Verify current ServiceCenter version by checking the running service or configuration files
- Review the ServiceComb 2.0.0 release notes for migration requirements and breaking changes
- Create a backup of current configuration files, data, and any custom settings
- Test the upgrade in a non-production environment first
- Upgrade ServiceComb ServiceCenter to version 2.0.0 or later using the appropriate package manager or build tool
- Verify the upgrade was successful by checking service functionality
- Validate that the directory traversal vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Servicecomb
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-21501 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data