Unauthenticated SSRF via verbose proxy errors
Published Jul 31, 2024 · Updated Jul 31, 2024
Server-side request forgery in Bitdefender GravityZone Update Server before 6.38.1-5 allows remote attackers to relay crafted requests. Bitdefender identifies verbose proxy error handling as the cause but has not disclosed the affected endpoint, input, or erroneous processing step. The unauthenticated network path exists only in on-premises deployments; public material does not identify the reachable internal resources or permitted follow-on actions.
Summary
What happened
Server-side request forgery in Bitdefender GravityZone Update Server before 6.38.1-5 allows remote attackers to relay crafted requests. Bitdefender identifies verbose proxy error handling as the cause but has not disclosed the affected endpoint, input, or erroneous processing step. The unauthenticated network path exists only in on-premises deployments; public material does not identify the reachable internal resources or permitted follow-on actions.
The record
- CVE
- CVE-2024-6980
- Published
- Jul 31, 2024
- Updated
- Jul 31, 2024
- Vendor
- Bitdefender
- Product
- GravityZone
- Classifications
- CWE-209, CAPEC-34, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2024CVE publishedPublication date reported by the CVE source.
- Jul 31, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.38.1-5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo