libIEC61850 1.3 ethernet_bsd.c Ethernet_receivePacket null pointer dereference
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libIEC61850 1.3. It has been declared as critical. Affected by this vulnerability is the function Ethernet_receivePacket
of the file ethernet_bsd.c. The manipulation as part of Packet leads to null pointer dereference.
This vulnerability is known as CVE-2018-19121. The attack can be launched remotely. There is no exploit available.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Details
A vulnerability was found in libIEC61850 1.3. It has been classified as critical. Affected is the function Ethernet_receivePacket
of the file ethernet_bsd.c. The manipulation as part of a Packet leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An issue has been found in libIEC61850 v1.3. It is a SEGV in Ethernet_receivePacket in ethernet_bsd.c.
The bug was discovered 11/08/2018. The weakness was presented 11/09/2018 (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2018-19121 since 11/09/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 1 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.
See VDB-126619 for similar entry. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
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
11/08/2018 🔍11/09/2018 🔍
11/09/2018 🔍
11/09/2018 🔍
11/10/2018 🔍
06/05/2023 🔍
Sources
Advisory: 85Status: Not defined
CVE: CVE-2018-19121 (🔍)
GCVE (CVE): GCVE-0-2018-19121
GCVE (VulDB): GCVE-100-126618
See also: 🔍
Entry
Created: 11/10/2018 08:04Updated: 06/05/2023 13:18
Changes: 11/10/2018 08:04 (58), 04/11/2020 11:41 (1), 06/05/2023 13:18 (3)
Complete: 🔍
Cache ID: 216:360:103
No comments yet. Languages: en.
Please log in to comment.