Firebase Cloud Messaging + Advance Admin Panel up to 2017-10-26 on iOS Push Notification login Username sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in Firebase Cloud Messaging + Advance Admin Panel up to 2017-10-26 on iOS. This vulnerability affects unknown code of the file /advance_push/public/login of the component Push Notification. The manipulation of the argument Username as part of Parameter leads to sql injection. This vulnerability is uniquely identified as CVE-2018-13850. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Firebase Cloud Messaging + Advance Admin Panel up to 2017-10-26 on iOS (Cloud Software). It has been rated as critical. This issue affects an unknown functionality of the file /advance_push/public/login of the component Push Notification. The manipulation of the argument username as part of a Parameter leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The "Firebase Cloud Messaging (FCM) + Advance Admin Panel" component supporting Firebase Push Notification on iOS (through 2017-10-26) allows SQL injection via the /advance_push/public/login username parameter.

The bug was discovered 07/08/2018. The weakness was disclosed 07/10/2018 (Website). The advisory is shared at cxsecurity.com. The identification of this vulnerability is CVE-2018-13850 since 07/10/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 are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 2 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.

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

Productinfo

Type

• Cloud Software

Vendor

• Firebase

Name

• Cloud Messaging + Advance Admin Panel

Version

• 2017-10-26

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