malware_floating-point
Differences
This shows you the differences between two versions of the page.
| malware_floating-point [2007/10/19 18:46] – created roumani | malware_floating-point [2007/10/19 18:50] (current) – roumani | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| This lecture covers two topics: malicious software and the representation / processing of real numbers. | This lecture covers two topics: malicious software and the representation / processing of real numbers. | ||
| + | |||
| ===== Outline ===== | ===== Outline ===== | ||
| * Self-modifying code | * Self-modifying code | ||
| - | * Buffer overrun on the stack and its exploitation | + | * Buffer overrun on the stack and its exploitation. The key idea is to overwrite the return address pushed on the stack. This way, when the method returns, it does not return to the caller but to the location specified by that address. That location has the malicious code. |
| * The IEEE 754 standard for representing real numbers in two formats, single (32-bit) and double (64-bit) precision. | * The IEEE 754 standard for representing real numbers in two formats, single (32-bit) and double (64-bit) precision. | ||
| * The floating-point instructions. | * The floating-point instructions. | ||
malware_floating-point.1192819605.txt.gz · Last modified: 2007/10/19 18:46 (external edit)