CVE-2017-7999
First published: Thu Jun 01 2017(Updated: )
Atlassian Eucalyptus before 4.4.1, when in EDGE mode, allows remote authenticated users with certain privileges to cause a denial of service (E2 service outage) via unspecified vectors.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Eucalyptus | =4.2.0 | |
| Eucalyptus | =4.2.1 | |
| Eucalyptus | =4.2.2 | |
| Eucalyptus | =4.3.0 | |
| Eucalyptus | =4.3.1 | |
| Eucalyptus | =4.4.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2017-7999?
CVE-2017-7999 is classified as a denial of service vulnerability affecting Atlassian Eucalyptus.
How do I fix CVE-2017-7999?
The recommended fix for CVE-2017-7999 is to upgrade to Atlassian Eucalyptus version 4.4.1 or later.
What versions of Eucalyptus are affected by CVE-2017-7999?
CVE-2017-7999 affects Eucalyptus versions 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, and 4.4.0.
Can CVE-2017-7999 be exploited remotely?
Yes, CVE-2017-7999 can be exploited by remote authenticated users with certain privileges.
What impact does CVE-2017-7999 have on services?
CVE-2017-7999 can lead to an E2 service outage in Atlassian Eucalyptus.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/author
- agent/references
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/eucalyptus
- canonical/eucalyptus
- version/eucalyptus/4.2.0
- version/eucalyptus/4.2.1
- version/eucalyptus/4.2.2
- version/eucalyptus/4.3.0
- version/eucalyptus/4.3.1
- version/eucalyptus/4.4.0