CVE-2021-22698
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 · uneditedA CWE-434: Unrestricted Upload of File with Dangerous Type vulnerability exists in the EcoStruxure Power Build - Rapsody software (V2.1.13 and prior) that could allow a stack-based buffer overflow to occur which could result in remote code execution when a malicious SSD file is uploaded and improperly parsed.
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 · moderate confidenceA CWE-434 unrestricted file upload vulnerability in EcoStruxure Power Build - Rapsody (v2.1.13 and prior) allows attackers to upload malicious SSD files that are improperly parsed, triggering a stack-based buffer overflow and enabling remote code execution.
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<= 2.1.13CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 the installed version of EcoStruxure Power Build - RapsodyLocate the application installation directory and check the version information in the product documentation, about screen, or version file typically found in the program files folder. Alternatively, check the Windows Programs and Features list or the software's main executable properties.Affected if The installed version is 2.1.13 or any version prior to it.
-
Verify if the application has an exposed file upload interfaceReview the application's web interface or any API endpoints that accept file uploads, specifically those related to SSD (System Structure Description) file handling. Check if unauthenticated or low-privilege users can access upload functionality.Affected if The application exposes any web portal or API endpoint that accepts SSD file uploads without proper restrictions.
-
Inspect file upload configuration settingsExamine the application's configuration files for settings related to file type validation, allowed extensions, and upload path restrictions. Look for any settings that control SSD file parsing behavior.Affected if File upload configuration lacks strict validation rules for SSD file types, or allows execution of uploaded files.
-
Check for Indicators of CompromiseReview server logs and file system for any uploaded .ssd files in unexpected directories, especially in web-accessible folders. Look for signs of anomalous SSD file uploads or parsing attempts.Affected if There are unexpected SSD files in web-accessible directories or logs show unusual SSD file upload patterns.
A system is affected if it runs EcoStruxure Power Build - Rapsody version 2.1.13 or earlier AND has an exposed file upload interface for SSD files.
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.
From vendor dataUpgrade to a patched version of EcoStruxure Power Build - Rapsody. Additionally, implement strict file type validation and content inspection for SSD files before parsing to block malicious uploads.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22698 — 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-22698 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