Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

July 30 2010

char
11:38

Bash #77489

<Jumper_> for an optimist the glass is half full, for a pessimist it is half empty, for an engineer it's twice as big as it needs to be
<Thraddash> for a programmer it has too few interfaces?
<Jumper_> for a programmer it's a Basic Input Output System (BIOS) with a buffer overflow just waiting to happen

February 17 2010

char
11:07

2010 CWE (Common Weakness Enumeration) / SANS: Top 25 Most Dangerous Programming Errors

table.char { border-collapse: collapse; } table.char td, table.char th { border: 1px solid #000; vertical-align: top; font: 10px Tahoma; background: #FFF; color: #000; } table.char th { font-weight: bold; } RankScoreIDName[1]346CWE-79Failure to Preserve Web Page Structure ('Cross-site Scripting')[2]330CWE-89Improper Sanitization of Special Elements used in an SQL Command ('SQL Injection')[3]273CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')[4]261CWE-352Cross-Site Request Forgery (CSRF)[5]219CWE-285Improper Access Control (Authorization)[6]202CWE-807Reliance on Untrusted Inputs in a Security Decision[7]197CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')[8]194CWE-434Unrestricted Upload of File with Dangerous Type[9]188CWE-78Improper Sanitization of Special Elements used in an OS Command ('OS Command Injection')[10]188CWE-311Missing Encryption of Sensitive Data[11]176CWE-798Use of Hard-coded Credentials[12]158CWE-805Buffer Access with Incorrect Length Value[13]157CWE-98Improper Control of Filename for Include/Require Statement in PHP Program ('PHP File Inclusion')[14]156CWE-129Improper Validation of Array Index[15]155CWE-754Improper Check for Unusual or Exceptional Conditions[16]154CWE-209Information Exposure Through an Error Message[17]154CWE-190Integer Overflow or Wraparound[18]153CWE-131Incorrect Calculation of Buffer Size[19]147CWE-306Missing Authentication for Critical Function[20]146CWE-494Download of Code Without Integrity Check[21]145CWE-732Incorrect Permission Assignment for Critical Resource[22]145CWE-770Allocation of Resources Without Limits or Throttling[23]142CWE-601URL Redirection to Untrusted Site ('Open Redirect')[24]141CWE-327Use of a Broken or Risky Cryptographic Algorithm[25]138CWE-362Race Condition

Allein unter diesen 25 gibt mit Sicherheit welche, deren Auswirkungen den meisten sicherlich gar nicht bewusst sind. Und versteht man erstmal alle 25 gilt es sicherzustellen, dass man diese auch zufriedenstellend verhindert. Der Schwachstellensucher kann exakt so denken, wie es die meisten Programmierer nicht können. Programmierer wollen immer den Gutfall und widmen sich allem anderen erst später. "Einbrecher" suchen sich ebenfalls den schwächsten Weg - und haben im erfolglosen Fall noch unzählige Alternativen...

Ob industrielle Software eher betroffen ist als Open-Source sollte man nicht beachten - in der Firma gibt es immer Deadlines, unter der jede Qualität natürlich leidet. Und in der Open-Source ist meist die Freizeit die Grenze von allem. In beiden Fällen gibt es überwiegend Leute, die sehr detailscheu sind und demzufolge wenig Fail-Safe-Strukturen bauen - womit sich Sicherheitslöcher am effektivsten stopfen (und v.a. auch noch gut erkennen) lassen.

Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.

Don't be the product, buy the product!

Schweinderl