FreeBSD up to 11.1/11.2 System Call freebsd4_getfsstat null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FreeBSD up to 11.1/11.2. It has been declared as problematic. The affected element is the function freebsd4_getfsstat of the component System Call Handler. Such manipulation leads to null pointer dereference.
This vulnerability is uniquely identified as CVE-2018-17154. Local access is required to approach this attack. No exploit exists.
Applying a patch is advised to resolve this issue.
Details
A vulnerability was found in FreeBSD up to 11.1/11.2 (Operating System) and classified as problematic. Affected by this issue is the function freebsd4_getfsstat of the component System Call Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. CVE summarizes:
In FreeBSD before 11.2-STABLE(r338987), 11.2-RELEASE-p4, and 11.1-RELEASE-p15, due to insufficient memory checking in the freebsd4_getfsstat system call, a NULL pointer dereference can occur. Unprivileged authenticated local users may be able to cause a denial of service.
The bug was discovered 09/27/2018. The weakness was disclosed 09/28/2018 (Website). The advisory is shared for download at security.FreeBSD.org. This vulnerability is handled as CVE-2018-17154 since 09/18/2018. The exploitation is known to be easy. The attack needs to be approached locally. No form of authentication is required for exploitation. There are known technical details, but no exploit is 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.
The entries VDB-124596 and VDB-124593 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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
09/18/2018 🔍09/27/2018 🔍
09/28/2018 🔍
09/28/2018 🔍
09/29/2018 🔍
05/19/2023 🔍
Sources
Product: freebsd.orgAdvisory: security.FreeBSD.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-17154 (🔍)
GCVE (CVE): GCVE-0-2018-17154
GCVE (VulDB): GCVE-100-124592
See also: 🔍
Entry
Created: 09/29/2018 07:40Updated: 05/19/2023 14:31
Changes: 09/29/2018 07:40 (44), 03/28/2020 08:37 (8), 05/19/2023 14:31 (13)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.