Facebook Katran IP Header bpf_xdp_adjust_head Identification initialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Facebook Katran. It has been rated as problematic. This affects the function bpf_xdp_adjust_head of the component IP Header Handler. Performing a manipulation of the argument Identification results in initialization.
This vulnerability is cataloged as CVE-2023-49062. It is possible to initiate the attack remotely. There is no exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Facebook Katran (Social Network Software) (version unknown). It has been classified as problematic. This affects the function bpf_xdp_adjust_head of the component IP Header Handler. The manipulation of the argument Identification with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. This is going to have an impact on confidentiality. The summary by CVE is:
Katran could disclose non-initialized kernel memory as part of an IP header. The issue was present for IPv4 encapsulation and ICMP (v4) Too Big packet generation. After a bpf_xdp_adjust_head call, Katran code didn’t initialize the Identification field for the IPv4 header, resulting in writing content of kernel memory in that field of IP header. The issue affected all Katran versions prior to commit 6a03106ac1eab39d0303662963589ecb2374c97f
The weakness was shared 11/28/2023. The advisory is shared at facebook.com. This vulnerability is uniquely identified as CVE-2023-49062 since 11/20/2023. Technical details are known, but no exploit is available.
Applying the patch 6a03106ac1eab39d0303662963589ecb2374c97f is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: 🔍
Exploiting
Class: InitializationCWE: CWE-665
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 6a03106ac1eab39d0303662963589ecb2374c97f
Timeline
11/20/2023 🔍11/28/2023 🔍
11/28/2023 🔍
12/17/2023 🔍
Sources
Advisory: 6a03106ac1eab39d0303662963589ecb2374c97fStatus: Confirmed
CVE: CVE-2023-49062 (🔍)
GCVE (CVE): GCVE-0-2023-49062
GCVE (VulDB): GCVE-100-246309
Entry
Created: 11/28/2023 17:20Updated: 12/17/2023 20:13
Changes: 11/28/2023 17:20 (42), 12/17/2023 20:05 (1), 12/17/2023 20:13 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.