CVE-2008-7023
First published: Fri Aug 21 2009(Updated: )
Aruba Mobility Controller running ArubaOS 3.3.1.16, and possibly other versions, installs the same default X.509 certificate for all installations, which allows remote attackers to bypass authentication. NOTE: this is only a vulnerability when the administrator does not follow recommendations in the product's security documentation.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Aruba Networks Aruba Mobility Controller | ||
| ArubaOS | =3.3.1.16 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2008-7023?
CVE-2008-7023 is considered a critical vulnerability as it allows remote attackers to bypass authentication.
How do I fix CVE-2008-7023?
To fix CVE-2008-7023, ensure that you replace the default X.509 certificate with a unique certificate during the setup of the Aruba Mobility Controller.
What versions of ArubaOS are affected by CVE-2008-7023?
CVE-2008-7023 specifically affects ArubaOS version 3.3.1.16, but may impact other versions if the default certificate is used.
Can CVE-2008-7023 be exploited remotely?
Yes, CVE-2008-7023 can be exploited remotely by attackers who can access the Aruba Mobility Controller.
Is there a workaround for CVE-2008-7023?
The primary workaround for CVE-2008-7023 is to immediately replace the default X.509 certificate to enhance security.
- collector/nvd-historical
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/arubanetworks
- canonical/aruba networks aruba mobility controller
- canonical/arubaos
- version/arubaos/3.3.1.16