1 / 8

Security Issues in Programming: Challenges and Risks

Learn about the security problems in programming, including coding bugs and design flaws, and how they can be exploited. Discover practical measures for writing secure code and the impact on performance and development costs.

ckahn
Download Presentation

Security Issues in Programming: Challenges and Risks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CITA 165 Section 6 Programming and Security in Programming

  2. Language Usage Statistics https://www.tiobe.com/tiobe-index/

  3. Security Problems in Programming • Most programmers never learned to produce secure code. • Secure code often takes a performance hit – i.e. the software runs about 1/3 slower – something many users don’t want to tolerate. • Writing secure code also takes a lot more time – hence, development costs are higher than usual. • Consequently, the longer development times and the longer running times discourage developers from writing secure code.

  4. Security Problems in Programming • Large quantities of computer code are written, debugged, published, and sold before all bugs are detected and resolved. • Combinations of certain software and hardware can reveal new software bugs. • Open Web Application Security Project (OWASP) is dedicated to helping organizations create/operate trustworthy software and publishes a list of top security risks. • OWASP Secure Coding Cheat Sheet • OWASP Secure Coding Guide

  5. CODING BUGS – 50% Information leakage Control hijacking Buffer overflow Smashing the stack Command injection Cross-site scripting Integer overflow Race conditions Formatted strings Segment overwrite Heap overflows Incomplete mediation SQL injection PHP include Non-trusted input Security Problems in Programming

  6. DESIGN FLAWS – 50% Cryptography misuse Lack of compartmentalization More privilege used than necessary Relying on secret algorithms Sharing resources Usability problems Security Problems in Programming

  7. Non-malicious Program Errors • Many of these problems are non-malicious, but they can be exploited to do nasty things. • A system exploit could be: • Attacker can execute arbitrary code • Attacker can gain access to a system • Attacker can put the system in an illegal state • Attacker can crash the program causing, for example, a denial of service

  8. Buffer Overflow Example • Word 2000 • Using Find/Replace with the Replace field larger than 200 characters caused a crash and wiped out any unsaved data.

More Related