Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

5/22/2014
12:00 PM
Jeff Williams
Jeff Williams
Commentary
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail vvv

The Only 2 Things Every Developer Needs To Know About Injection

There's no simple solution for preventing injection attacks. There are effective strategies that can stop them in their tracks.
3 of 3

3 of 3
Comment  | 
Print  | 
Comments
Oldest First  |  Newest First  |  Threaded View
Charlie Babcock
100%
0%
Charlie Babcock,
User Rank: Ninja
5/22/2014 | 11:20:09 PM
Succinct anti-injection advice
Excellent, succinct advice on how to combat the injection attack. It requires more than most programmers are prepared to understand and do, but  there must be some way for greater programmer awareness and framework automated assistance to reduce the frequency of these attacks.
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
5/23/2014 | 4:35:43 AM
Data Validation
It's all about the data validation.  OWASP has great documents on this, including: https://www.owasp.org/index.php/Data_Validation and https://www.owasp.org/index.php/Interpreter_Injection

In a nutshell:
  • Integrity checks - Ensure that the data has not been tampered with and is the same as before (checksums, logic in test code, etc)
  • Validation - Ensure that the data is strongly typed, correct syntax, within length boundaries, contains only permitted characters, or that numbers are correctly signed and within range boundaries
  • Business rules - Ensure that data is not only validated, but business rule correct. For example, interest rates fall within permitted boundaries. (extensive test scripts based upon code requirements)
cumulonimbus
50%
50%
cumulonimbus,
User Rank: Apprentice
5/23/2014 | 12:29:50 PM
Responsible programming
Excellent article! In your example of injection, the encapsulation would have to be prepared in such a way as to return multiple data. I am not sure most api would work this way, but it is certainly something to be aware of as sometimes developers do use such shortcuts and multi-purpose code.

When data is coming from a public source I believe that validation must necessarily occur using multiple factors, both for authentication and sanity checks. Perhaps there is more trust within a corporate shield, but these days this is rarely the case. Take for example a (trusted) employee using a BYOD device on corporate wi-fi, even with MAC validation.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9079
PUBLISHED: 2020-08-11
FusionSphere OpenStack 8.0.0 have a protection mechanism failure vulnerability. The product incorrectly uses a protection mechanism. An attacker has to find a way to exploit the vulnerability to conduct directed attacks against the affected product.
CVE-2020-16275
PUBLISHED: 2020-08-10
A cross-site scripting (XSS) vulnerability in the Credential Manager component in SAINT Security Suite 8.0 through 9.8.20 could allow arbitrary script to run in the context of a logged-in user when the user clicks on a specially crafted link.
CVE-2020-16276
PUBLISHED: 2020-08-10
An SQL injection vulnerability in the Assets component of SAINT Security Suite 8.0 through 9.8.20 allows a remote, authenticated attacker to gain unauthorized access to the database.
CVE-2020-16277
PUBLISHED: 2020-08-10
An SQL injection vulnerability in the Analytics component of SAINT Security Suite 8.0 through 9.8.20 allows a remote, authenticated attacker to gain unauthorized access to the database.
CVE-2020-16278
PUBLISHED: 2020-08-10
A cross-site scripting (XSS) vulnerability in the Permissions component in SAINT Security Suite 8.0 through 9.8.20 could allow arbitrary script to run in the context of a logged-in user when the user clicks on a specially crafted link.