CVE-2021-35211
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 · uneditedMicrosoft discovered a remote code execution (RCE) vulnerability in the SolarWinds Serv-U product utilizing a Remote Memory Escape Vulnerability. If exploited, a threat actor may be able to gain privileged access to the machine hosting Serv-U Only. SolarWinds Serv-U Managed File Transfer and Serv-U Secure FTP for Windows before 15.2.3 HF2 are affected by this vulnerability.
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 confidenceRemote code execution vulnerability in SolarWinds Serv-U Managed File Transfer and Serv-U Secure FTP for Windows. The flaw is a remote memory escape vulnerability that, if exploited, allows a threat actor to gain privileged access to the machine hosting the affected Serv-U instance.
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< 15.2.3= 15.2.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Verify Serv-U installation existsCheck for Serv-U installation directory (commonly C:\Program Files\SolarWinds\Serv-U\) or look for Serv-U service via 'sc query' commandAffected if Serv-U is not installed on the system
-
Retrieve installed Serv-U versionOpen Serv-U Administration, navigate to About or version info, or check the executable properties of Serv-U.exe in the installation directoryAffected if Version is less than 15.2.3 or exactly 15.2.3 (not 15.2.3 HF2 or later)
-
Confirm Serv-U service is runningRun 'sc query Serv-U' or check Services.msc to verify the Serv-U service statusAffected if Serv-U service is running and version is in the affected range
-
Verify authentication is enabledCheck Serv-U administration console or configuration for user authentication settingsAffected if Local or remote authentication is enabled with a vulnerable Serv-U version
If Serv-U is installed and the running version is 15.2.3 or any version prior to 15.2.3 HF2, the environment is affected by this vulnerability.
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 · scoped15.2.3
Upgrade SolarWinds Serv-U to version 15.2.3 HF2 or later. Given the CVSS 10 critical rating and evidence of active exploitation potential, this patch should be prioritized for immediate deployment.
Serv-U 15.2.3 HF2 or later
- 1. Identify the current Serv-U version by checking the SolarWinds Serv-U installation
- 2. Download Serv-U version 15.2.3 HF2 or later from the official SolarWinds download portal
- 3.备份当前的Serv-U配置文件和数据
- 4.按照SolarWinds官方的升级文档执行升级操作
- 5.验证升级成功并确认服务正常运行
- 6.确认漏洞已修复，通过检查版本信息确认已运行15.2.3 HF2或更高版本
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35211 — 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-35211 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