Hanwha Vision HRX-1620 up to 3.05.62 inadequate encryption

Summaryinfo

A vulnerability was found in Hanwha Vision HRX-1620 up to 3.05.62. It has been rated as problematic. This issue affects some unknown processing. Performing a manipulation results in inadequate encryption. This vulnerability is identified as CVE-2023-6096. The attack is only possible with local access. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Hanwha Vision HRX-1620 up to 3.05.62. This affects an unknown function. The manipulation with an unknown input leads to a inadequate encryption vulnerability. CWE is classifying the issue as CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. This is going to have an impact on confidentiality. The summary by CVE is:

Vladimir Kononovich, a Security Researcher has found a flaw that using a inappropriate encryption logic on the DVR. firmware encryption is broken and allows to decrypt. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.

The advisory is shared at hanwhavision.com. This vulnerability is uniquely identified as CVE-2023-6096 since 11/13/2023. The exploitability is told to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 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

• Hanwha Vision

Name

• HRX-1620

Version

• 3.05.0
• 3.05.1
• 3.05.2
• 3.05.3
• 3.05.4
• 3.05.5
• 3.05.6
• 3.05.7
• 3.05.8
• 3.05.9
• 3.05.10
• 3.05.11
• 3.05.12
• 3.05.13
• 3.05.14
• 3.05.15
• 3.05.16
• 3.05.17
• 3.05.18
• 3.05.19
• 3.05.20
• 3.05.21
• 3.05.22
• 3.05.23
• 3.05.24
• 3.05.25
• 3.05.26
• 3.05.27
• 3.05.28
• 3.05.29
• 3.05.30
• 3.05.31
• 3.05.32
• 3.05.33
• 3.05.34
• 3.05.35
• 3.05.36
• 3.05.37
• 3.05.38
• 3.05.39
• 3.05.40
• 3.05.41
• 3.05.42
• 3.05.43
• 3.05.44
• 3.05.45
• 3.05.46
• 3.05.47
• 3.05.48
• 3.05.49
• 3.05.50
• 3.05.51
• 3.05.52
• 3.05.53
• 3.05.54
• 3.05.55
• 3.05.56
• 3.05.57
• 3.05.58
• 3.05.59
• 3.05.60
• 3.05.61
• 3.05.62

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