Unknown
CVE-2024-47659
CVE ID
AttackerKB requires a CVE ID in order to pull vulnerability data and references from the CVE list and the National Vulnerability Database. If available, please supply below:
Add References:
CVE-2024-47659
MITRE ATT&CK
Collection
Command and Control
Credential Access
Defense Evasion
Discovery
Execution
Exfiltration
Impact
Initial Access
Lateral Movement
Persistence
Privilege Escalation
Topic Tags
Description
In the Linux kernel, the following vulnerability has been resolved:
smack: tcp: ipv4, fix incorrect labeling
Currently, Smack mirrors the label of incoming tcp/ipv4 connections:
when a label ‘foo’ connects to a label ‘bar’ with tcp/ipv4,
‘foo’ always gets ‘foo’ in returned ipv4 packets. So,
- returned packets are incorrectly labeled (‘foo’ instead of ‘bar’)
- ‘bar’ can write to ‘foo’ without being authorized to write.
Here is a scenario how to see this:
Take two machines, let’s call them C and S,
with active Smack in the default state
(no settings, no rules, no labeled hosts, only builtin labels)At S, add Smack rule ‘foo bar w’
(labels ‘foo’ and ‘bar’ are instantiated at S at this moment)At S, at label ‘bar’, launch a program
that listens for incoming tcp/ipv4 connectionsFrom C, at label ‘foo’, connect to the listener at S.
(label ‘foo’ is instantiated at C at this moment)
Connection succeedes and works.Send some data in both directions.
Collect network traffic of this connection.
All packets in both directions are labeled with the CIPSO
of the label ‘foo’. Hence, label ‘bar’ writes to ‘foo’ without
being authorized, and even without ever being known at C.
If anybody cares: exactly the same happens with DCCP.
This behavior 1st manifested in release 2.6.29.4 (see Fixes below)
and it looks unintentional. At least, no explanation was provided.
I changed returned packes label into the ‘bar’,
to bring it into line with the Smack documentation claims.
Add Assessment
No one has assessed this topic. Be the first to add your voice to the community.
CVSS V3 Severity and Metrics
General Information
Vendors
- linux
Products
- linux kernel
References
Miscellaneous
Additional Info
Technical Analysis
Report as Emergent Threat Response
Report as Exploited in the Wild
CVE ID
AttackerKB requires a CVE ID in order to pull vulnerability data and references from the CVE list and the National Vulnerability Database. If available, please supply below: