Gallagher Controller up to 8.20 Key insufficiently protected credentials

Summaryinfo

A vulnerability identified as problematic has been detected in Gallagher Controller up to 7.80/7.90/8.00/8.10/8.20. Affected by this issue is some unknown functionality. The manipulation leads to insufficiently protected credentials (Key). This vulnerability is documented as CVE-2020-16097. The attack needs to be performed locally. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Gallagher Controller up to 7.80/7.90/8.00/8.10/8.20. It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability (Key). Using CWE to declare the problem leads to CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. Impacted is confidentiality. The summary by CVE is:

On controllers running versions of v8.20 prior to vCR8.20.200221b (distributed in v8.20.1093(MR2)), v8.10 prior to vGR8.10.179 (distributed in v8.10.1211(MR5)), v8.00 prior to vGR8.00.165 (Distributed in v8.00.1228(MR6)), v7.90 prior to vGR7.90.165 (distributed in v7.90.1038(MRX)), v7.80 or earlier, It is possible to retrieve site keys used for securing MIFARE Plus and Desfire using debug ports on T Series readers.

The weakness was released 09/15/2020 (Website). The advisory is shared at security.gallagher.com. The identification of this vulnerability is CVE-2020-16097 since 07/28/2020. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

Applying a patch is able to eliminate this problem.

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

Productinfo

Vendor

• Gallagher

Name

• Controller

Version

• 7.0
• 7.1
• 7.2
• 7.3
• 7.4
• 7.5
• 7.6
• 7.7
• 7.8
• 7.9
• 7.10
• 7.11
• 7.12
• 7.13
• 7.14
• 7.15
• 7.16
• 7.17
• 7.18
• 7.19
• 7.20
• 7.21
• 7.22
• 7.23
• 7.24
• 7.25
• 7.26
• 7.27
• 7.28
• 7.29
• 7.30
• 7.31
• 7.32
• 7.33
• 7.34
• 7.35
• 7.36
• 7.37
• 7.38
• 7.39
• 7.40
• 7.41
• 7.42
• 7.43
• 7.44
• 7.45
• 7.46
• 7.47
• 7.48
• 7.49
• 7.50
• 7.51
• 7.52
• 7.53
• 7.54
• 7.55
• 7.56
• 7.57
• 7.58
• 7.59
• 7.60
• 7.61
• 7.62
• 7.63
• 7.64
• 7.65
• 7.66
• 7.67
• 7.68
• 7.69
• 7.70
• 7.71
• 7.72
• 7.73
• 7.74
• 7.75
• 7.76
• 7.77
• 7.78
• 7.79
• 7.80
• 7.81
• 7.82
• 7.83
• 7.84
• 7.85
• 7.86
• 7.87
• 7.88
• 7.89
• 7.90
• 8.0
• 8.00
• 8.1
• 8.2
• 8.3
• 8.4
• 8.5
• 8.6
• 8.7
• 8.8
• 8.9
• 8.10
• 8.11
• 8.12
• 8.13
• 8.14
• 8.15
• 8.16
• 8.17
• 8.18
• 8.19
• 8.20

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