| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Citilog 8.0. This affects an unknown part. Executing a manipulation can lead to channel accessible. The identification of this vulnerability is CVE-2022-28860. There is no exploit available.
Details
A vulnerability has been found in Citilog 8.0 and classified as critical. This vulnerability affects an unknown part. The manipulation with an unknown input leads to a channel accessible vulnerability. The CWE definition for the vulnerability is CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An authentication downgrade in the server in Citilog 8.0 allows an attacker (in a man in the middle position between the server and its smart camera Axis M1125) to achieve HTTP access to the camera.
The weakness was shared 07/22/2022. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-28860 since 04/08/2022. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1557.
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 EUVD (EUVD-2022-33297). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Channel accessibleCWE: CWE-300
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/08/2022 🔍07/22/2022 🔍
07/22/2022 🔍
05/20/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-28860 (🔍)
GCVE (CVE): GCVE-0-2022-28860
GCVE (VulDB): GCVE-100-204844
EUVD: 🔍
Entry
Created: 07/22/2022 08:52Updated: 05/20/2026 21:21
Changes: 07/22/2022 08:52 (36), 08/20/2022 07:43 (11), 05/20/2026 21:21 (15)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.