<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://charlesreid1.com/w/index.php?action=history&amp;feed=atom&amp;title=Kali%2FLayer_6_Attacks</id>
	<title>Kali/Layer 6 Attacks - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://charlesreid1.com/w/index.php?action=history&amp;feed=atom&amp;title=Kali%2FLayer_6_Attacks"/>
	<link rel="alternate" type="text/html" href="https://charlesreid1.com/w/index.php?title=Kali/Layer_6_Attacks&amp;action=history"/>
	<updated>2026-06-20T04:16:13Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.12</generator>
	<entry>
		<id>https://charlesreid1.com/w/index.php?title=Kali/Layer_6_Attacks&amp;diff=30663&amp;oldid=prev</id>
		<title>Admin: Create Layer 6 (Presentation) Attacks page (via create-page on MediaWiki MCP Server)</title>
		<link rel="alternate" type="text/html" href="https://charlesreid1.com/w/index.php?title=Kali/Layer_6_Attacks&amp;diff=30663&amp;oldid=prev"/>
		<updated>2026-06-19T05:53:53Z</updated>

		<summary type="html">&lt;p&gt;Create Layer 6 (Presentation) Attacks page (via create-page on MediaWiki MCP Server)&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;=Presentation (Layer 6) Attacks=&lt;br /&gt;
&lt;br /&gt;
This page covers the use of Kali to carry out attacks on layer 6, the presentation layer. Also see [[Kali/Workflow]].&lt;br /&gt;
&lt;br /&gt;
==Review==&lt;br /&gt;
&lt;br /&gt;
Let&amp;#039;s review the network stack before we launch into network layer attacks.&lt;br /&gt;
&lt;br /&gt;
{{NetworkStack}}&lt;br /&gt;
&lt;br /&gt;
Layer 6 is the Presentation layer. It handles data representation and formatting, including character encoding, data compression, and encryption/decryption.&lt;br /&gt;
&lt;br /&gt;
==Scenario==&lt;br /&gt;
&lt;br /&gt;
The presentation layer is where data is transformed into a format that the application layer can understand. This includes SSL/TLS encryption and decryption, character encoding conversions, and data compression. Attacks at this layer typically focus on manipulating how data is represented, encrypted, or encoded.&lt;br /&gt;
&lt;br /&gt;
Unlike lower-layer attacks that require physical proximity or network access, presentation-layer attacks can often be carried out remotely, since they target the way data is formatted before it reaches the application.&lt;br /&gt;
&lt;br /&gt;
==SSL/TLS Downgrade Attacks==&lt;br /&gt;
&lt;br /&gt;
{{Main|SSLStrip}}&lt;br /&gt;
&lt;br /&gt;
While SSL/TLS straddles multiple layers, the encryption/decryption function is squarely a presentation-layer concern. [[SSLStrip]] is a tool that performs an SSL downgrade attack, forcing HTTPS connections to fall back to HTTP. This allows an attacker to read traffic in cleartext that would otherwise be encrypted.&lt;br /&gt;
&lt;br /&gt;
==SSL/TLS Cipher Attacks==&lt;br /&gt;
&lt;br /&gt;
{{Main|MITM/HTTPS}}&lt;br /&gt;
&lt;br /&gt;
Tools like [[Sslscan]] and [[Testssl.sh]] can probe a server&amp;#039;s supported ciphers, identifying weak or deprecated ciphers that can be exploited. The attacker may force the server to negotiate a weaker cipher suite (a downgrade attack at the cipher level), making encrypted traffic easier to crack. This is a presentation-layer attack because it targets the encryption algorithm negotiation that occurs during the TLS handshake.&lt;br /&gt;
&lt;br /&gt;
==Certificate Attacks==&lt;br /&gt;
&lt;br /&gt;
{{Main|Certificates}}&lt;br /&gt;
{{Main|SSLSniff}}&lt;br /&gt;
&lt;br /&gt;
The X.509 certificate system, part of the presentation layer&amp;#039;s encryption framework, can be attacked in several ways. [[SSLSniff]] allows an attacker to serve up fake certificates to sheep during a man-in-the-middle attack. Self-signed certificates or certificates from compromised certificate authorities can be presented to a sheep, who may not verify them properly.&lt;br /&gt;
&lt;br /&gt;
See [[Certificates]] for more detail on forging and manipulating certificates.&lt;br /&gt;
&lt;br /&gt;
==Encoding Attacks==&lt;br /&gt;
&lt;br /&gt;
Because the presentation layer handles character encoding, attacks can target encoding conversions. Double-encoding attacks, Unicode normalization attacks, and overlong UTF-8 sequences can be used to bypass security filters at higher layers. These attacks exploit the fact that the presentation layer may interpret encoded data differently than the application layer expects.&lt;br /&gt;
&lt;br /&gt;
For example, a web application firewall might reject &amp;lt;code&amp;gt;../&amp;lt;/code&amp;gt; in a URL, but the presentation layer might first decode &amp;lt;code&amp;gt;%2e%2e%2f&amp;lt;/code&amp;gt; into &amp;lt;code&amp;gt;../&amp;lt;/code&amp;gt; — and if the WAF checks before decoding occurs, the traversal passes through.&lt;br /&gt;
&lt;br /&gt;
==Format String Attacks==&lt;br /&gt;
&lt;br /&gt;
Format string vulnerabilities occur when a program uses user-controlled input as a format string in functions like &amp;lt;code&amp;gt;printf()&amp;lt;/code&amp;gt;. This is a presentation-layer concern because format strings control how data is represented when displayed or processed. Tools like [[GDB]] and the [[MSF|Metasploit Framework]] can be used to develop format string exploits.&lt;br /&gt;
&lt;br /&gt;
==Compression Side-Channel Attacks==&lt;br /&gt;
&lt;br /&gt;
Attacks like CRIME (Compression Ratio Info-leak Made Easy) and BREACH (Browser Reconnaissance and Exfiltration via Adaptive Compression of Hypertext) exploit data compression in HTTPS to leak encrypted session cookies. These attacks work at the presentation layer because compression and decompression are presentation-layer functions. By injecting controlled plaintext into a compressed HTTPS stream and measuring the resulting size, an attacker can infer the value of secret tokens like session cookies.&lt;br /&gt;
&lt;br /&gt;
=Flags=&lt;br /&gt;
&lt;br /&gt;
{{KaliAttackLayersFlag}}&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
</feed>