FreeBSD up to 10.4/11.1/11.2 IPv6 Protocol Control Block Flag null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in FreeBSD up to 10.4/11.1/11.2. Affected is an unknown function of the component IPv6 Protocol Control Block Flag Handler. The manipulation results in null pointer dereference. This vulnerability is identified as CVE-2018-6925. The attack is only possible with local access. There is not any exploit available. It is advisable to implement a patch to correct this issue.
Details
A vulnerability classified as problematic has been found in FreeBSD up to 10.4/11.1/11.2 (Operating System). Affected is an unknown part of the component IPv6 Protocol Control Block Flag Handler. The manipulation with an unknown input 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 availability. CVE summarizes:
In FreeBSD before 11.2-STABLE(r338986), 11.2-RELEASE-p4, 11.1-RELEASE-p15, 10.4-STABLE(r338985), and 10.4-RELEASE-p13, due to improper maintenance of IPv6 protocol control block flags through various failure paths, an unprivileged authenticated local user may be able to cause a NULL pointer dereference causing the kernel to crash.
The bug was discovered 09/27/2018. The weakness was released 09/28/2018 (Website). The advisory is shared for download at security.FreeBSD.org. This vulnerability is traded as CVE-2018-6925 since 02/11/2018. The exploitability is told to be easy. The attack needs to be approached locally. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
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.
Applying a patch is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-124593 and VDB-124592. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://www.freebsd.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: 🔍
Physical: Partially
Local: Yes
Remote: No
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
02/11/2018 🔍09/27/2018 🔍
09/28/2018 🔍
09/28/2018 🔍
09/29/2018 🔍
03/28/2020 🔍
Sources
Product: freebsd.orgAdvisory: security.FreeBSD.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-6925 (🔍)
GCVE (CVE): GCVE-0-2018-6925
GCVE (VulDB): GCVE-100-124596
See also: 🔍
Entry
Created: 09/29/2018 07:41Updated: 03/28/2020 08:51
Changes: 09/29/2018 07:41 (58), 03/28/2020 08:51 (2)
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.