2010
DOI: 10.48550/arxiv.1005.1925
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Information Hiding Using Improper Frame Padding

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2022
2022
2022
2022

Publication Types

Select...
2

Relationship

2
0

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 0 publications
0
2
0
Order By: Relevance
“…However, our intention is not to generalize while losing descriptive detail. To cover all special variants of new patterns that combine the ideas of multiple original patterns, the following pattern descriptions cover all related aspects in their description: [5], showing that unused/reserved fields in IEEE 802.3 and 802.5 [56]- [58], IPv4 [56], IP-IP, IPv6 [51], TCP [56], [59], ICMP [60], [61], BACnet [62], DHCP [63], and IPSec [59]…”
Section: Pt12 Retransmission [5]mentioning
confidence: 99%
“…However, our intention is not to generalize while losing descriptive detail. To cover all special variants of new patterns that combine the ideas of multiple original patterns, the following pattern descriptions cover all related aspects in their description: [5], showing that unused/reserved fields in IEEE 802.3 and 802.5 [56]- [58], IPv4 [56], IP-IP, IPv6 [51], TCP [56], [59], ICMP [60], [61], BACnet [62], DHCP [63], and IPSec [59]…”
Section: Pt12 Retransmission [5]mentioning
confidence: 99%
“…E2. [5], showing that unused/reserved fields in IEEE 802.3 and 802.5 [56]- [58], IPv4 [56], IP-IP, IPv6 [51], TCP [56], [59], ICMP [60], [61], BACnet [62], DHCP [63], and IPSec [59] can be exploited by overwriting certain header fields, such as the IP Identifier. Moreover, additional and recent works have shown that more protocols are vulnerable due to their unused/reserved fields, such as ii) MQTT [53] and iii) SIP [64].…”
Section: Ps3mentioning
confidence: 99%