LiveActive security incident?Get immediate response
CVE Record

CVE-2008-7023: Aruba Mobility Controller running ArubaOS 3.3.1.16, and possibly other versions, installs the same default...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Some Aruba Mobility Controllers reportedly shipped with the same default X.509 certificate. If an administrator left that default in place, authentication could be bypassed. This appears configuration-dependent and tied at least to ArubaOS 3.3.1.16, with other versions only described as possible. Exposure is most plausible in legacy Aruba Mobility Controller deployments running ArubaOS 3.3.1.16, or possibly nearby versions, where the default certificate was never replaced. Organizations without asset records for old wireless controllers should treat exposure as uncertain until configuration is checked. Treat this as a targeted legacy exposure review, not an emergency based on current evidence. The business concern is unauthorized access to wireless infrastructure if old controllers still use factory credentials or certificates. Mitigation focus: Inventory Aruba Mobility Controllers and record ArubaOS versions.; Check Aruba security documentation and support guidance for affected versions.; Replace any factory default certificate with a unique trusted certificate..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2008-7023 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.