Lutron Quantum BACnet Integration up to 2.0 User Authentication /deviceIP information disclosure

Summaryinfo

A vulnerability marked as problematic has been reported in Lutron Quantum BACnet Integration up to 2.0. The impacted element is an unknown function of the file /deviceIP of the component User Authentication. The manipulation leads to information disclosure. This vulnerability is documented as CVE-2018-8880. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Lutron Quantum BACnet Integration up to 2.0. It has been rated as problematic. This issue affects an unknown code of the file /deviceIP of the component User Authentication. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

Lutron Quantum BACnet Integration 2.0 (firmware 3.2.243) doesn't check for correct user authentication before showing the /deviceIP information, which leads to internal network information disclosure.

The bug was discovered 04/19/2018. The weakness was released 04/23/2018 as EDB-ID 44488 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2018-8880 since 03/20/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.

After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (44488). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Lutron

Name

• Quantum BACnet Integration

Version

• 2.0

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion