Bugs gone bad
Stories Columns Opinions Resources
Sun extends Groovy, PHP support to NetBeans
Version 6.5 of the IDE will see complete support for those two languages along with comple...
|
Sun reorganizes its software production infrastructure
Facing economic hardships, lost revenue and loss of employees, Sun has split its software ...
|
Adobe steers Flash toward RIA implementation
At this year's Adobe MAX Conference, the focus was on Flash, this time making Flash more o...
|
BigLever builds a bridge to SCM with Gears
The Gears Universal Configuration Management Bridge allows CM systems to integrate with Ge...
|
SOA Watch: New economic realities
In the current economic downturn, agile programming and SOA are attractive options that bu...
|
Integration Watch: A new twist on threads
The key to raising the efficiency of multiprocessors is to shrink the overall workload by ...
|
Integration Watch: The Return of NetRexx?
Java scripting languages are seeing a surge in popularity, with NetRexx looking particular...
|
Windows & .NET Watch: Transaction crowd gets a boost
With multicore chips becoming the standard for processors, the need for a flexible, usable...
|
From the Editors: Election should shake up JCP
Rod Johnson has the right ideas for opening up the Java Community Process, and he may be a...
|
Letters to the Editor: Sun gives REST, SOAP choice
A reader takes issue with a headline on our story about Sun working with REST along with S...
|
Guest View: Be smart and lazy
The optimal solution for problems is the simplest one, so always aim to streamline your ap...
|
Zeichick's Take: From EXEC to EXEC 2 to REXX to NetRexx
Andrew Binstock's column last week, "The Return of NetRexx," brought back some fond memori...
|
Practical tips for saving money on code maintenance
If software design is expensive, well, code maintenance is even more so. When you look...
|
Transform your app-dev quality by involving the whole community in testing
As the saying goes, the more eyes you have on software, the shallower the bugs. That’...
|
Build your dev and test labs for less – a lot less – with virtualization
You don’t have the budget to equip developers and software test teams with all the har...
|
Software Common Hacks and Counterattacks: A Guide to Protecting Software Products against the Top 7 Piracy Threats
Software piracy continues to be a growing epidemic. This white paper examines prevalen...
|
By SD Times News Team
August 1, 2008 —
Static analyzers can identify and locate these security-related bugs:
Cross-site scripting: Causes the browser to execute arbitrary client-side scripting code, hijacking the user’s session and allowing the attacker to phish for account/financial information.
Injection flaws: Improperly validated data passing through the interpreter can “confuse” it and open the way for malicious code to be injected into the interpreter.
Buffer overflows: Mostly a C and C++ problem due to lack of memory, buffer overflows are similar to injection attacks; in this case, an attacker sends commands with too many characters and takes over the system, with full privileges.
Insecure direct object reference: Intentional or unintentional access to internal object handlers leads to exposure of data.
Information leakage and improper error handling: Overly helpful error messages cough up too much information about a system—version, system type, error type, etc.—giving an attacker more knowledge to launch exploits.
Resource leak: When programs leak memory, the operating system may terminate them for exceeding prescribed limits, affecting other programs on the computer. Attackers can then exploit the remaining processes, in much the same way as a buffer overflow.
Unintentional ignored expressions: When expressions are ignored, code is unreachable and cannot perform needed action. For example, a bug discovered by a Coverity customer, in which a missing parenthesis kept a single routine from executing, turned out to be the worst exploit that company had seen in five years, according to Ben Chelf, founding CTO at Coverity.
Null pointer de-reference: Invalid values assigned between operations lead to a hard crash, the most frequent cause of Windows’ Blue Screen of Death.
Web services: Malicious code can be injected into Web services entry points. Static analyzers include rule wizards and data APIs that perform cross-service analysis and identification of Web services entry points.
Custom cookies/hidden fields: Attackers can view the underlying HTTP response payload by viewing the source code of a Web page or by using proxies to find hidden files and cookies, and then modifying values to try to break developers’ assumptions and gain control of the application.
Sources: Coverity, Ounce Labs
Related Search Term(s): Security, testing & troubleshooting
Share this link: http://www.sdtimes.com/link/32547