This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Native Methods"
From OWASP
Dinis.cruz (talk | contribs) |
Dinis.cruz (talk | contribs) |
||
| Line 1: | Line 1: | ||
The moment you see native methods (which leave the Java security manager and memory protection), you know you found an area that might contain potential Buffer Overflows, or other C++ type vulnerabilities. | The moment you see native methods (which leave the Java security manager and memory protection), you know you found an area that might contain potential Buffer Overflows, or other C++ type vulnerabilities. | ||
| − | In the .Net Framework this is even more problematic due to the high usage of unmanaged COM objects (Note to Dinis: Put here details about his 'Buffer | + | In the .Net Framework this is even more problematic due to the high usage of unmanaged COM objects (Note to Dinis: Put here details about his 'Buffer Overflows on the .Net Framework' Research) |
Revision as of 15:10, 18 January 2007
The moment you see native methods (which leave the Java security manager and memory protection), you know you found an area that might contain potential Buffer Overflows, or other C++ type vulnerabilities.
In the .Net Framework this is even more problematic due to the high usage of unmanaged COM objects (Note to Dinis: Put here details about his 'Buffer Overflows on the .Net Framework' Research)
