Java Insecurity: Accounting for Subtleties That Can Compromise Code

Authors:
Charlie Lai
Affiliations:
Sun Microsystems
Venue:
IEEE Software
Year:
2008

Citing 0
Cited 4

Securing Java code: heuristics and an evaluation of static analysis tools

Proceedings of the 2008 workshop on Static analysis
Classification of Component Vulnerabilities in Java Service Oriented Programming (SOP) Platforms

CBSE '08 Proceedings of the 11th International Symposium on Component-Based Software Engineering
The developer is the enemy

Proceedings of the 2008 workshop on New security paradigms
Incident-centered information security: Managing a strategic balance between prevention and response

Information and Management

Quantified Score

Hi-index	0.00

Visualization

Abstract

Java developers commonly follow numerous coding guidelines—such as minimizing accessibility, creating copies of mutable inputs, and preventing the unauthorized construction of sensitive classes—to ensure that their programs are safe. Various subtleties related to each guideline could lead to unexpected behavior, and ultimately to security vulnerabilities. Java developers can safely account for these subtleties to prevent attacks. This article is part of a special issue on Security for the Rest of Us.