CVE-2021-3552
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 Server-Side Request Forgery (SSRF) vulnerability in the EPPUpdateService component of Bitdefender Endpoint Security Tools allows an attacker to proxy requests to the relay server. This issue affects: Bitdefender Endpoint Security Tools versions prior to 6.6.27.390; versions prior to 7.1.2.33. Bitdefender GravityZone 6.24.1-1.
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 confidenceAn SSRF vulnerability in the EPPUpdateService component of Bitdefender Endpoint Security Tools allows attackers to proxy requests through the affected server to the relay server, potentially enabling internal network reconnaissance or bypassing network restrictions.
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< 6.2.21.160>= 6.6.27.0, < 6.6.27.390>= 7.0.0.00, < 7.1.2.33= 6.24.1-1CVSS 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.
-
Verify EPPUpdateService is presentCheck Windows services list for 'EPPUpdateService' or look for related update service processes in Task Manager. On Linux, check for eppupdateservice or similar processes.Affected if The EPPUpdateService component exists and is running on the system
-
Check installed Bitdefender Endpoint Security Tools versionOpen Windows Registry at HKLM\SOFTWARE\Bitdefender\EndpointSecurity or check the product UI under About/Version information. On Linux, run 'bdsecd --version' or check /opt/BitDefender/etc/info.ini.Affected if The version is less than 6.2.21.160, OR between 6.6.27.0 and 6.6.27.389, OR between 7.0.0.00 and 7.1.2.32
-
Check Bitdefender GravityZone version if applicableLog into the GravityZone console and navigate to Administration > System Information, or check the appliance version via its management interface.Affected if GravityZone version equals exactly 6.24.1-1
-
Verify update service network configurationExamine firewall rules and service binding configuration to determine if the EPPUpdateService listens on network-accessible interfaces. Check for exposed ports in the service configuration files.Affected if The EPPUpdateService is bound to accessible network interfaces without proper access restrictions
A system is affected if it runs a vulnerable version of Bitdefender Endpoint Security Tools (within the listed ranges) or GravityZone 6.24.1-1, AND has the EPPUpdateService component enabled and network-accessible.
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 · scoped6.2.21.1606.6.27.3907.1.2.33
Upgrade Bitdefender Endpoint Security Tools to version 6.6.27.390/7.1.2.33 or later, and ensure GravityZone is updated to address this vulnerability.
Endpoint Security Tools: upgrade to 6.6.27.390 or later for 6.6.x branch, or 7.1.2.33 or later for 7.x branch; GravityZone: upgrade to a version newer than 6.24.1-1
- Identify the currently installed Bitdefender Endpoint Security Tools or GravityZone version
- For Endpoint Security Tools 6.2.x versions: upgrade to version 6.2.21.160 or later
- For Endpoint Security Tools 6.6.x versions (>= 6.6.27.0): upgrade to version 6.6.27.390 or later
- For Endpoint Security Tools 7.0.x and 7.1.x versions: upgrade to version 7.1.2.33 or later
- For GravityZone version 6.24.1-1: contact Bitdefender support for the patched release or upgrade to a newer stable version
- After upgrade, verify the EPPUpdateService component has been updated and is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3552 — 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-3552 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