Alcatel-Lucent OmniAccess Certificate information disclosure ⚔ [Disputed]

Summaryinfo

A vulnerability was found in Alcatel-Lucent OmniAccess. It has been rated as problematic. The impacted element is an unknown function of the component Certificate. Performing a manipulation results in information disclosure. The attack must be initiated from a local position. There is no exploit available. It is still unclear if this vulnerability genuinely exists. It is advisable to use the suggested workaround.

Detailsinfo

A vulnerability was found in Alcatel-Lucent OmniAccess (version unknown). It has been classified as problematic. This affects an unknown function of the component Certificate. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.

The bug was discovered 05/15/2015. The weakness was shared 09/06/2016 by Stefan Viehböck with SEC Consult Vulnerability Lab as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The vendor cooperated in the coordination of the public release. The exploitability is told to be easy. An attack has to be approached locally. The successful exploitation requires a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue. The advisory points out:

browser-trusted certificate (CN: securelogin.arubanetworks.com, signed by GeoTrust) including its private key is embedded in the firmware of several Aruba Networks/Alcatel-Lucent products. The certificate is used for providing user access to a captive portal and web administration via HTTPS as well as EAP connections for WPA2-Enterprise clients. An attacker can use this vulnerability to impersonate a captive portal, web administration or Wi-Fi AP and gain access to sensitive information. The certificate is compromised and should be revoked. Users should be told to install certificates generated by themselves.

The vulnerability was handled as a non-public zero-day exploit for at least 480 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment.

The best possible mitigation is suggested to be Workaround. The mailinglist post contains the following remark:

The certificate "securelogin.arubanetworks.com", and its associated private key, is distributed on every controller and in every software release.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Alcatel-Lucent

Name

• OmniAccess

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion