Update Server: Improper Handling of Length Parameter Inconsistency
CVE-2022-0677 is a high-severity improper handling of length parameter inconsistency vulnerability in Update Server from Bitdefender, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 3.4.0.276 as the first without the flaw, so updating Update Server to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.25% chance of exploitation within 30 days, higher than 70% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Update Server to 3.4.0.276 or a later version.
- Update GravityZone to 26.4-1 or a later version.
- Update Endpoint Security Tools for Linux to 6.2.21.171 or a later version.
- Read the advisory on bitdefender.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Bitdefender | Update Server | before 3.4.0.276 | 3.4.0.276 |
| Bitdefender | GravityZone | before 26.4-1 | 26.4-1 |
| Bitdefender | Endpoint Security Tools for Linux | before 6.2.21.171 | 6.2.21.171 |
| Bitdefender | Endpoint Security Tools for Windows | before 7.4.1.111 | 7.4.1.111 |
| Bitdefender | Endpoint Security Tools | before 6.2.21.171; before 7.4.1.111 | 6.2.21.171, 7.4.1.111 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (bitdefender.com) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
Improper Handling of Length Parameter Inconsistency vulnerability in the Update Server component of Bitdefender Endpoint Security Tools (in relay role), GravityZone (in Update Server role) allows an attacker to cause a Denial-of-Service. This issue affects: Bitdefender Update Server versions prior to 3.4.0.276. Bitdefender GravityZone versions prior to 26.4-1. Bitdefender Endpoint Security Tools for Linux versions prior to 6.2.21.171. Bitdefender Endpoint Security Tools for Windows versions prior to 7.4.1.111.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Handling of Length Parameter Inconsistency
The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.
How developers prevent this class of flaw
- When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.
- Do not let the user control the size of the buffer.
- Validate that the length of the user-supplied data is consistent with the buffer size.
More Improper Handling of Length Parameter Inconsistency vulnerabilities (CWE-130)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Recent Improper Handling of Length Parameter Inconsistency vulnerabilities
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.