OWASP - User contributions [en]

Expression Language Injection

2013-04-15T19:32:53Z

Dan Amodio:

{{Vulnerability}}

Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''

[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]

==Description==

Expression Language (EL) Injection happens when attacker controlled data enters an EL interpreter.

With EL implementations prior to 2.2, attacker can recover sensitive server side information available through implicit objects. This includes model objects, beans, session scope, application scope, etc. The EL 2.2 spec allows method invocation, which permits an attacker to execute arbitrary code within context of the application. This can manipulate application functionality, expose sensitive data, and branch out into system code access-- posing a risk of server compromise.

A specific pattern exists in certain version of the Spring Framework, where Spring JSP tags will double resolve EL. In versions prior to 3.0.6, it is not possible to disable this functionality, and the pattern must be avoided.

==Risk Factors==

The likelihood of this issue is '''Medium''', for the following reasons:
*Certain attack scenarios are not overly sophisticated, although require some skill.
*Automated tools may begin to pick up on the pattern, increasing the likelihood of discovery.
*Attackers are highly motivated to discover code execution vulnerabilities.

The overall impact of this issue is '''High''', for the following reasons:
* An attacker could modify and invoke functionality on the application server.
* Unauthorized access to data and functionality, as well as account hijacking and remote code execution.
* Confidentiality, and Integrity concerns from a successful attack.

==Examples==

=== Spring Message Tag ===
The Spring Message tag will double resolve Expression Language.

A common pattern of passing URL parameters to the message tag is:

Controller.java
@RequestMapping(value="/")
String index() {

if ( hasErrors() ) {
return "redirect:/error?msg=error.generic";
} else {
return "index";
}

}

error.jsp
<spring:message code="${param.msg}" />

A URL request to the above code of the form:
?msg=${param.test}&test=INJECTION

Will result in the string literal "INJECTION" being passed to the message tag. The application should respond with an exception like:

No message found under code 'INJECTION' for locale 'en_US'

Accordingly, the attacker could submit methods within the EL like:
?msg=${pageContext.request.getSession().setAttribute("admin",true)}

If the container provided EL interpreter does not support static class methods ( java.lang.Runtime.getCurrentRuntime().exec() ), an attacker can use a URLClassLoader to load remote code.

=== Spring Eval Tag ===
Spring Framework provides a JSP tag that interprets Spring Expression Language (SpEL).

The following code would be vulnerable:
<spring:eval expression="${param.vulnerable}" />

A URL of the following form would provide system code access:
?vulnerable=T(java.lang.Runtime).getRuntime().exec(“cmd.exe”)

==Related [[Attacks]]==

* [[Interpreter Injection]]

==Related [[Vulnerabilities]]==

* [[Reflection injection]]
* [[Injection problem]]

==Related [[Controls]]==
Avoid putting user data into an expression interpreter if possible. Otherwise, validate and/or encode the data to ensure it is not evaluated as expression language.
* [[Input_Validation]]

In the case of Spring Framework, disable the double resolution functionality in versions 3.0.6 and above by placing the following configuration in the application web.xml.

<context-param>
<description>Spring Expression Language Support</description>
<param-name>springJspExpressionSupport</param-name>
<param-value>false</param-value>
</context-param>

==Related [[Technical Impacts]]==
* [[Loss of accountability]]
* [[Loss of availability]]
* [[Loss of confidentiality]]
* [[Loss of integrity]]

==References==
* [http://cwe.mitre.org/data/definitions/917.html CWE 917].
* [http://support.springsource.com/security/cve-2011-2730 Spring Framework: CVE-2011-2730]
* [http://www.mindedsecurity.com/fileshare/ExpressionLanguageInjection.pdf EL Injection: Information Disclosure]
* [http://danamodio.com/application-security/discoveries/spring-remote-code-with-expression-language-injection/ EL Injection: Remote Code Execution]
* [http://jcp.org/aboutJava/communityprocess/mrel/jsr245/index.html JSR245: EL 2.2 Spec]

{{Stub}}

[[Category:Input Validation Vulnerability]]
[[Category:Vulnerability]]

Expression Language Injection

2013-04-15T19:21:35Z

Dan Amodio:

{{Vulnerability}}

Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''

[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]

==Description==

Expression Language (EL) Injection happens when attacker controlled data enters an EL interpreter.

With EL implementations prior to 2.2, attacker can recover sensitive server side information available through implicit objects. This includes model objects, beans, session scope, application scope, etc. The EL 2.2 spec allows method invocation, which permits an attacker to execute arbitrary code within context of the application. This can manipulate application functionality, expose sensitive data, and branch out into system code access-- posing a risk of server compromise.

A specific pattern exists in certain version of the Spring Framework, where Spring JSP tags will double resolve EL. In versions prior to 3.0.6, it is not possible to disable this functionality, and the pattern must be avoided.

==Risk Factors==

The likelihood of this issue is '''Medium''', for the following reasons:
*Certain attack scenarios are not overly sophisticated, although require some skill.
*Automated tools may begin to pick up on the pattern, increasing the likelihood of discovery.
*Attackers are highly motivated to discover code execution vulnerabilities.

The overall impact of this issue is '''High''', for the following reasons:
* An attacker could modify and invoke functionality on the application server.
* Unauthorized access to data and functionality, as well as account hijacking and remote code execution.
* Confidentiality, and Integrity concerns from a successful attack.

==Examples==

=== Spring Message Tag ===
The Spring Message tag will double resolve Expression Language.

A common pattern of passing URL parameters to the message tag is:

Controller.java
@RequestMapping(value="/")
String index() {

if ( hasErrors() ) {
return "redirect:/error?msg=error.generic";
} else {
return "index";
}

}

error.jsp
<spring:message code="${param.msg}" />

A URL request to the above code of the form:
?msg=${param.test}&test=INJECTION

Will result in the string literal "INJECTION" being passed to the message tag. The application should respond with an exception like:

No message found under code 'INJECTION' for locale 'en_US'

Accordingly, the attacker could submit methods within the EL like:
?msg=${pageContext.request.getSession().setAttribute("admin",true)}

==Related [[Attacks]]==

* [[Interpreter Injection]]

==Related [[Vulnerabilities]]==

* [[Reflection injection]]
* [[Injection problem]]

==Related [[Controls]]==
Avoid putting user data into an expression interpreter if possible. Otherwise, validate and/or encode the data to ensure it is not evaluated as expression language.
* [[Input_Validation]]

In the case of Spring Framework, disable the double resolution functionality in versions 3.0.6 and above by placing the following configuration in the application web.xml.

<context-param>
<description>Spring Expression Language Support</description>
<param-name>springJspExpressionSupport</param-name>
<param-value>false</param-value>
</context-param>

==Related [[Technical Impacts]]==
* [[Loss of accountability]]
* [[Loss of availability]]
* [[Loss of confidentiality]]
* [[Loss of integrity]]

==References==
* [http://cwe.mitre.org/data/definitions/917.html CWE 917].
* [http://support.springsource.com/security/cve-2011-2730 Spring Framework: CVE-2011-2730]
* [http://www.mindedsecurity.com/fileshare/ExpressionLanguageInjection.pdf EL Injection: Information Disclosure]
* [http://danamodio.com/application-security/discoveries/spring-remote-code-with-expression-language-injection/ EL Injection: Remote Code Execution]
* [http://jcp.org/aboutJava/communityprocess/mrel/jsr245/index.html JSR245: EL 2.2 Spec]

{{Stub}}

[[Category:Input Validation Vulnerability]]
[[Category:Vulnerability]]

Expression Language Injection

2013-04-15T19:12:07Z

Dan Amodio: Initial add for EL Injection, CWE 917

{{Vulnerability}}

Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''

[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]

==Description==

Expression Language (EL) Injection happens when attacker controlled data enters an EL interpreter.

With EL implementations prior to 2.2, attacker can recover sensitive server side information available through implicit objects. This includes model objects, beans, session scope, application scope, etc. The EL 2.2 spec allows method invocation, which permits an attacker to execute arbitrary code within context of the application. This can manipulate application functionality, expose sensitive data, and branch out into system code access-- posing a risk of server compromise.

A specific pattern exists in certain version of the Spring Framework, where Spring JSP tags will double resolve EL. In versions prior to 3.0.6, it is not possible to disable this functionality, and the pattern must be avoided.

==Risk Factors==

TBD

==Examples==

=== Spring Message Tag ===
The Spring Message tag will double resolve Expression Language.

A common pattern of passing URL parameters to the message tag is:

Controller.java
@RequestMapping(value="/")
String index() {

if ( hasErrors() ) {
return "redirect:/error?msg=error.generic";
} else {
return "index";
}

}

error.jsp
<spring:message code="${param.msg}" />

A URL request to the above code of the form:
?msg=${param.test}&test=INJECTION

Will result in the string literal "INJECTION" being passed to the message tag. The application should respond with an exception like:

No message found under code 'INJECTION' for locale 'en_US'

Accordingly, the attacker could submit methods within the EL like:
?msg=${pageContext.request.getSession().setAttribute("admin",true)}

==Related [[Attacks]]==

* [[Interpreter Injection]]

==Related [[Vulnerabilities]]==

* [[Reflection injection]]
* [[Injection problem]]

==Related [[Controls]]==
Avoid putting user data into an expression interpreter if possible. Otherwise, validate and/or encode the data to ensure it is not evaluated as expression language.
* [[Input_Validation]]

In the case of Spring Framework, disable the double resolution functionality in versions 3.0.6 and above by placing the following configuration in the application web.xml.

<context-param>
<description>Spring Expression Language Support</description>
<param-name>springJspExpressionSupport</param-name>
<param-value>false</param-value>
</context-param>

==Related [[Technical Impacts]]==
* [[Loss of accountability]]
* [[Loss of availability]]
* [[Loss of confidentiality]]
* [[Loss of integrity]]

==References==
* [http://cwe.mitre.org/data/definitions/917.html CWE 917].
* [http://support.springsource.com/security/cve-2011-2730 Spring Framework: CVE-2011-2730]
* [http://www.mindedsecurity.com/fileshare/ExpressionLanguageInjection.pdf EL Injection: Information Disclosure]
* [http://danamodio.com/application-security/discoveries/spring-remote-code-with-expression-language-injection/ EL Injection: Remote Code Execution]
* [http://jcp.org/aboutJava/communityprocess/mrel/jsr245/index.html JSR245: EL 2.2 Spec]

{{Stub}}

[[Category:Input Validation Vulnerability]]
[[Category:Vulnerability]]

User:Dan Amodio

2013-04-09T19:25:05Z

Dan Amodio:

*[https://www.owasp.org/index.php/Projects/OWASP_ESAPI_C_Project OWASP ESAPI C] Project Leader
*[https://www.owasp.org/index.php/Projects/OWASP_ESAPI_C%2B%2B_Project OWASP ESAPI C++] Contributor
*Mobile security enthusiast
*Consultant at [http://www.aspectsecurity.com Aspect Security] - [mailto:dan.amodio@aspectsecurity.com dan.amodio@aspectsecurity.com]

OWASP ESAPI C++ Project

2012-04-01T14:51:51Z

Dan Amodio:

==== Main ====

==== Project About ====
{{:Projects/OWASP ESAPI C++ Project | Project About}}

__NOTOC__ <headertabs />

[[Category:OWASP_Project|ESAPI C++ Project]]
[[Category:OWASP_Tool]]
[[Category:OWASP_Alpha_Quality_Tool]]

User:Dan Amodio

2012-02-14T22:42:34Z

Dan Amodio:

*[https://www.owasp.org/index.php/Projects/OWASP_ESAPI_C_Project OWASP ESAPI C] Project Leader
*[https://www.owasp.org/index.php/Projects/OWASP_ESAPI_C%2B%2B_Project OWASP ESAPI C++] Contributor
*Consultant at [http://www.aspectsecurity.com Aspect Security]

Projects/OWASP ESAPI C Project

2012-02-14T22:37:47Z

Dan Amodio:

{{Template:<includeonly>{{{1}}}</includeonly><noinclude>Project About</noinclude>
| project_name = OWASP ESAPI C Project
| project_home_page = :Category:OWASP Enterprise Security API
| project_description = This is the C language version of the OWASP ESAPI.
*ESAPI for C is sponsored by the United States Government
*An API for helping programmers develop more secure business applications in C.
*Provides easy to use functions for proper auditing, simple wrappers for cryptographic functions, and more.
| project_license =
| leader_name1 = Dan Amodio
| leader_email1 = dan.amodio@aspectsecurity.com
| leader_username1 = Dan_Amodio
| contributor_name1 = David Anderson
| contributor_email1 = david.anderson@aspectsecurity.com
| contributor_username1 =
| pamphlet_link =
| presentation_link =
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp-esapi-c
| project_road_map =
| links_url1 = http://code.google.com/p/owasp-esapi-c/
| links_name1 = ESAPI-C Google Code Project
| links_url2 = http://owasp-esapi-c.googlecode.com/svn/trunk/doc/html/index.html
| links_name2 = ESAPI-C Documentation
| release_1 =
| release_2 =
| release_3 =
| release_4 =

| project_about_page = Projects/OWASP ESAPI C Project
}}
<noinclude>[[Category: Project About]]</noinclude>

OWASP ESAPI C Project

2012-01-18T15:13:01Z

Dan Amodio:

= Project About =
{{:Projects/OWASP ESAPI C Project | Project About}}

__NOTOC__ <headertabs />

[[Category:OWASP_Project|ESAPI C Project]]
[[Category:OWASP_Tool]]
[[Category:OWASP_Alpha_Quality_Tool]]

Category:OWASP Enterprise Security API

2012-01-18T15:09:52Z

Dan Amodio: Fixed tabs (broke with wiki upgrade). Also, there is a bug with tab names that have a period or any special characters.

= Home =

{| width="100%"
|-
! width="66%" |
! width="33%" |
|- valign="top"
|
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library that makes it easier for programmers to write lower-risk applications. The ESAPI libraries are designed to make it easier for programmers to retrofit security into existing applications. The ESAPI libraries also serve as a solid foundation for new development.

Allowing for language-specific differences, all OWASP ESAPI versions have the same basic design:

*'''There is a set of security control interfaces.''' They define for example types of parameters that are passed to types of security controls.

*'''There is a reference implementation for each security control.''' The logic is not organization‐specific and the logic is not application‐specific. An example: string‐based input validation.

*'''There are optionally your own implementations for each security control.''' There may be application logic contained in these classes which may be developed by or for your organization. An example: enterprise authentication.

This project source code is licensed under the [http://en.wikipedia.org/wiki/BSD_license BSD license], which is very permissive and about as close to public domain as is possible. The project documentation is licensed under the [http://creativecommons.org/licenses/by-sa/2.0/ Creative Commons] license. You can use or modify ESAPI however you want, even include it in commercial products.

The following organizations are a few of the many organizations that are starting to adopt ESAPI to secure their web applications: [http://www.americanexpress.com/ American Express], [http://www.apache.org/ Apache Foundation], [http://www.boozallen.com Booz Allen Hamilton], [http://www.aspectsecurity.com/ Aspect Security], [http://www.foundstone.com Foundstone(McAfee)], [http://www.thehartford.com/ The Hartford], [http://www.infinitecampus.com Infinite Campus], [http://www.lockheedmartin.com/ Lockheed Martin], [http://cwe.mitre.org/top25/index.html MITRE], [http://enterprise.spawar.navy.mil/ U.S. Navy - SPAWAR], [http://www.worldbank.org/ The World Bank], [http://www.sans.org/top25errors/ SANS Institute].

Please let us know how your organization is using OWASP ESAPI. Include your name, organization's name, and brief description of how you are using it. The project lead can be reached [mailto:jeff.williams@owasp.org here]. The project maintainer can be reached [mailto:jim.manico@owasp.org here].

|
[[Image:Esapi-sponsors.PNG]]

|}

{| width="100%"
|-
! width="33%" |
! width="33%" |
! width="33%" |
|- valign="top"
|
== Let's talk here ==

[[Image:Asvs-bulb.jpg]]'''ESAPI Communities'''

Further development of ESAPI occurs through mailing list discussions and occasional workshops, and suggestions for improvement are welcome. For more information, please subscribe to one of the lists below.

*[https://lists.owasp.org/mailman/listinfo/esapi-dev esapi-dev mailing list (this is the main list)]
*[https://lists.owasp.org/mailman/listinfo/esapi-user esapi-user mailing list]
*[https://lists.owasp.org/mailman/listinfo/esapi-php esapi-php mailing list]
*[https://lists.owasp.org/mailman/listinfo/esapi-python esapi-python mailing list]
*[https://lists.owasp.org/mailman/listinfo/owasp-esapi-ruby esapi-ruby mailing list]
*[https://lists.owasp.org/mailman/listinfo/owasp-esapi-swingset esapi-swingset mailing list]
*[http://groups.google.com/group/cfesapi esapi-coldfusion mailing list]

IRC Chat

If you would rather chat with us about your problem or thoughts - you can join us in our IRC channel using an [http://www.google.com/search?q=irc+client IRC Client] or using FreeNode's [http://webchat.freenode.net WebChat] client.

*Server: irc.freenode.net
*Channel: #esapi

|

== Got developer cycles? ==

[[Image:Asvs-waiting.JPG]]'''ESAPI Coding'''

The ESAPI project is always on the lookout for volunteers who are interested in contributing developer cycles.

*[http://owasp-esapi-php.googlecode.com/files/esapi4php-contributing.pdf ESAPI for PHP Developer Onboarding Instructions]
*ESAPI for other languages developer onboarding instructions -- coming soon!

|
== Related resources ==

[[Image:Asvs-satellite.jpg]]'''OWASP Cheat Sheet Series'''

*[[SQL Injection Prevention Cheat Sheet]]
*[[XSS (Cross Site Scripting) Prevention Cheat Sheet]]
*[[Cryptographic Storage Cheat Sheet]]
*[[Authentication Cheat Sheet]]
*[[Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet]]
*[[Transport Layer Protection Cheat Sheet]]

|}

= Downloads =

{| width="100%"
|-
! width="33%" |
! width="33%" |
|- valign="top"
|
[[Image:Asvs-step1.jpg]]'''1. About ESAPI'''

*Data sheet([http://www.owasp.org/images/8/81/Esapi-datasheet.pdf PDF],[http://www.owasp.org/images/3/32/Esapi-datasheet.doc Word])
*Project presentation ([http://owasp-esapi-java.googlecode.com/files/OWASP%20ESAPI.ppt PowerPoint])
*Video presentation ([http://www.youtube.com/watch?v=QAPD1jPn04g YouTube])

[[Image:Asvs-step2.jpg]]'''2. Get ESAPI'''

*[http://code.google.com/p/owasp-esapi-java/downloads/list ESAPI for Java Downloads]
*{{#switchtablink:.NET|ESAPI for .NET}} 
*{{#switchtablink:Classic ASP|ESAPI for Classic ASP}} 
*{{#switchtablink:PHP|ESAPI for PHP}} 
*{{#switchtablink:ColdFusion.2FCFML|ESAPI for ColdFusion & CFML}} 
*{{#switchtablink:Python|ESAPI for Python}} 
*[http://code.google.com/p/owasp-esapi-js/downloads/detail?name=esapi4js-0.1.3.zip ESAPI for Javascript] 

|
[[Image:Asvs-step3.jpg]]'''3. Learn ESAPI'''

*ESAPI design patterns (not language-specific): [http://www.owasp.org/images/8/82/Esapi-design-patterns.pdf (PDF], [http://www.owasp.org/index.php/File:Esapi-design-patterns.doc Word], [http://www.owasp.org/images/8/87/Esapi-design-patterns.ppt PPT)]
*The [[ESAPI Swingset|ESAPI Swingset]] sample application demonstrates how to leverage ESAPI to protect a web application.
*LAMP should be spelled LAMPE ([http://www.owasp.org/images/a/ac/LAMP_Should_be_Spelled_LAMPE.pdf PDF])
*ESAPI for Java interface documentation ([http://owasp-esapi-java.googlecode.com/svn/trunk_doc/index.html JavaDocs])
*ESAPI for PHP interface documentation ([http://owasp-esapi-php.googlecode.com/svn/trunk_doc/latest/index.html phpdoc])

|}

= What I did with ESAPI =

*I used ESAPI for Java with Google AppEngine. I used it for simple validation and encoding. --[mailto:jeff.williams@owasp.org Jeff]

*I used ESAPI for PHP with a custom web 2.0 corporate knowledge management application, made up of many open source and commercial applications integrated to work together. I added an organization- and application-specific "Adapter" control to wrap calls to the other ESAPI controls. --[mailto:mike.boberski@owasp.org Mike]

*I used ESAPI for Java’s "Logger" control to make it easier for a US Government customer to meet C&A requirements. --[mailto:dave.wichers@owasp.org Dave]

*I used ESAPI for Java to build a low risk web application that was over 250,000+ lines of code in size. --[mailto:jim.manico@owasp.org Jim]

*I used ESAPI for Java's "Authenticator" to replace a spaghetti-like mechanism in a legacy financial services web application. In hindsight I should have used the application-specific "Adapter" pattern mentioned by Mike above. The organization also uses the ESAPI Encryptor as an interface to a hardware security module. --[mailto:roman.hustad@yahoo.com Roman]

*I use ESAPI for Java to educate developers about application security principals at several of the world’s largest organizations. --[mailto:jim.manico@owasp.org Jim] 

= Glossary =

[[Image:Asvs-letters.jpg]]'''ESAPI Terminology'''

*'''adapter''' - There are optionally your own implementations for each security control. There may be application logic contained in these classes which may be developed by or for your organization. The logic may be organization-specific and/or application-specific. There may be proprietary information or logic contained in these classes which may be developed by or for your organization.
*'''built-in singleton design pattern''' - The "built-in" singleton design pattern refers to the replacement of security control reference implementations with your own implementations. ESAPI interfaces are otherwise left intact.
*'''codec''' - ESAPI encoder/decoder reference implementations.
*'''core''' - The ESAPI interfaces and reference implementations that are not intended to be replaced with enterprise-specific versions are called the ESAPI Core.
*'''exception''' - ESAPI exception reference implementations.
*'''extended factory design pattern''' - The "extended" factory design pattern refers to the addition of a new security control interface and corresponding implementation, which in turn calls ESAPI security control reference implementations and/or security control reference implementations that were replaced with your own implementations. The ESAPI locator class would be called in order to retrieve a singleton instance of your new security control, which in turn would call ESAPI security control reference implementations and/or security control reference implementations that were replaced with your own implementations.
*'''extended singleton design pattern''' - The "extended" singleton pattern refers to the replacement of security control reference implementations with your own implementations and the addition/modification/subtraction of corresponding security control interfaces.
*'''ES-enable (or ESAPI-enable)''' - Just as web applications and web services can be Public Key Infrastructure (PKI) enabled (PK-enabled) to perform for example certificate-based authentication, applications and services can be OWASP ESAPI-enabled (ES-enabled) to enable applications and services to protect themselves from attackers.
*'''filter''' - In ESAPI for Java, there is additionally an HTTP filter that can be called separately from the other controls.
*'''interfaces''' - There is a set of security control interfaces. There is no application logic contained in these interfaces. They define for example types of parameters that are passed to types of security controls. There is no proprietary information or logic contained in these interfaces.
*'''locator''' - The ESAPI security control interfaces include an "ESAPI" class that is commonly referred to as a "locator" class. The ESAPI locator class is called in order to retrieve singleton instances of individual security controls, which are then called in order to perform security checks (such as performing an access control check) or that result in security effects (such as generating an audit record).
*'''reference implementation''' - There is a reference implementation for each security control. There is application logic contained in these classes, i.e. contained in these interface implementations. However, the logic is not organization-specific and the logic is not application-specific. There is no proprietary information or logic contained in these reference implementation classes.
*'''Web Application Firewall (WAF)''' - In ESAPI for Java, there is additionally a Web Application Firewall (WAF) that can be called separately from the other controls.

 

= Java EE =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_Java_EE_Version | OWASP Project Identification Tab}}

= Dot NET =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_.NET_Version | OWASP Project Identification Tab}}

= Classic ASP =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_Classic_ASP_Version | OWASP Project Identification Tab}}

= PHP =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_PHP_Version | OWASP Project Identification Tab}}

= ColdFusion CFML =


{{:Projects/OWASP ESAPI for ColdFusion - CFML Project | Project About}}

= Python =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_Python_Version | OWASP Project Identification Tab}}

= JavaScript =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_JavaScript_Version | OWASP Project Identification Tab}}

= Objective C =

{{:Projects/OWASP ESAPI Objective - C Project | Project About}}

= Force com =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API_-_Force.com_Version | OWASP Project Identification Tab}}

= Ruby =

{{:Projects/Owasp Esapi Ruby | Project About}}

= Swingset =

The ESAPI Swingset Project divides itself into sub-projects, i.e., [[Projects/OWASP ESAPI Swingset Interactive Project|Swingset Interactive]] and [[Projects/OWASP ESAPI Swingset Demo Project|Swingset Demo]].

= ESAPI C =

{{:Projects/OWASP ESAPI C Project | Project About}}

= ESAPI CPP =

{{:Projects/OWASP ESAPI C++ Project | Project About}}

= ESAPI Perl =

{{:Projects/OWASP ESAPI Perl Project | Project About}}

= Project Details =

{{:GPC_Project_Details/OWASP_Enterprise_Security_API | OWASP Project Identification Tab}}

__NOTOC__ <headertabs /> 

{{OWASP Builders}}

Projects/OWASP ESAPI C++ Project

2011-08-01T17:04:12Z

Dan Amodio:

{{Template:<includeonly>{{{1}}}</includeonly><noinclude>Project About</noinclude>
| project_name = OWASP ESAPI C++ Project
| project_home_page = :Category:OWASP Enterprise Security API
| project_description =This is the C++ language version of the OWASP ESAPI.
*ESAPI for C++ is sponsored by the United States Government
*An API for helping programmers develop more secure business applications in C++.
*Provides easy to use functions for proper auditing, simple wrappers for cryptographic functions, and more.
| project_license =
| leader_name1 =David Anderson
| leader_email1 =david.anderson@aspectsecurity.com
| leader_username[1-10] =
| contributor_name1 = Dan Amodio
| contributor_email1 = dan.amodio@aspectsecurity.com
| contributor_username1 = Dan_Amodio
| contributor_name2 = Kevin Wall
| contributor_email2 = kevin.w.wall@gmail.com
| contributor_username2 = Kevin_W._Wall
| contributor_name3 = Jeff Walton
| contributor_email3 =
| contributor_username3 = Jeffrey_Walton
| pamphlet_link =
| presentation_link =
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp-esapi-c++
| project_road_map =
| links_url1 = ESAPI C++ Google Code Project
| links_name1 = http://code.google.com/p/owasp-esapi-cplusplus/
| release_1 =
| release_2 =
| release_3 =
| release_4 =

| project_about_page = Projects/OWASP ESAPI C++ Project
}}
<noinclude>[[Category: Project About]]</noinclude>

Projects/OWASP ESAPI C++ Project

2011-08-01T14:35:57Z

Dan Amodio:

{{Template:<includeonly>{{{1}}}</includeonly><noinclude>Project About</noinclude>
| project_name = OWASP ESAPI C++ Project
| project_home_page = :Category:OWASP Enterprise Security API
| project_description =This is the C++ language version of the OWASP ESAPI.
*ESAPI for C++ is sponsored by the United States Government
*An API for helping programmers develop more secure business applications in C++.
*Provides easy to use functions for proper auditing, simple wrappers for cryptographic functions, and more.
| project_license =
| leader_name1 =David Anderson
| leader_email1 =david.anderson@aspectsecurity.com
| leader_username[1-10] =
| contributor_name1 = Dan Amodio
| contributor_email1 = dan.amodio@aspectsecurity.com
| contributor_username1 = Dan_Amodio
| contributor_name2 = Kevin Wall
| contributor_email2 =
| contributor_username2 = Kevin_W._Wall
| contributor_name3 = Jeff Walton
| contributor_email3 =
| contributor_username3 = Jeffrey_Walton
| pamphlet_link =
| presentation_link =
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp-esapi-c++
| project_road_map =
| links_url1 = ESAPI C++ Google Code Project
| links_name1 = http://code.google.com/p/owasp-esapi-cplusplus/
| release_1 =
| release_2 =
| release_3 =
| release_4 =

| project_about_page = Projects/OWASP ESAPI C++ Project
}}
<noinclude>[[Category: Project About]]</noinclude>

Projects/OWASP ESAPI C++ Project

2011-08-01T14:33:57Z

Dan Amodio:

{{Template:<includeonly>{{{1}}}</includeonly><noinclude>Project About</noinclude>
| project_name = OWASP ESAPI C++ Project
| project_home_page = :Category:OWASP Enterprise Security API
| project_description =This is the C++ language version of the OWASP ESAPI.
*ESAPI for C++ is sponsored by the United States Government
*An API for helping programmers develop more secure business applications in C++.
*Provides easy to use functions for proper auditing, simple wrappers for cryptographic functions, and more.
| project_license =
| leader_name1 =David Anderson
| leader_email1 =david.anderson@aspectsecurity.com
| leader_username[1-10] =
| contributor_name1 = Dan_Amodio
| contributor_email1 = dan.amodio@aspectsecurity.com
| contributor_username1 = Dan Amodio
| contributor_name2 = Kevin Wall
| contributor_email2 =
| contributor_username2 = Kevin_W._Wall
| contributor_name3 = Jeff Walton
| contributor_email3 =
| contributor_username3 = Jeffrey_Walton
| pamphlet_link =
| presentation_link =
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp-esapi-c++
| project_road_map =
| links_url1 = ESAPI C++ Google Code Project
| links_name1 = http://code.google.com/p/owasp-esapi-cplusplus/
| release_1 =
| release_2 =
| release_3 =
| release_4 =

| project_about_page = Projects/OWASP ESAPI C++ Project
}}
<noinclude>[[Category: Project About]]</noinclude>

User:Dan Amodio

2011-07-15T19:40:10Z

Dan Amodio:

[http://www.aspectsecurity.com Aspect Security]

Projects/OWASP ESAPI C Project

2011-07-15T18:56:35Z

Dan Amodio:

{{Template:<includeonly>{{{1}}}</includeonly><noinclude>Project About</noinclude>
| project_name = OWASP ESAPI C Project
| project_home_page = :Category:OWASP Enterprise Security API
| project_description = This is the C language version of the OWASP ESAPI.
*ESAPI for C is sponsored by the United States Government
*An API for helping programmers develop more secure business applications in C.
*Provides easy to use functions for proper auditing, simple wrappers for cryptographic functions, and more.
| project_license =
| leader_name1 =David Anderson
| leader_email1 = david.anderson@aspectsecurity.com
| leader_username1 =
| contributor_name1 = Dan Amodio
| contributor_email1 = dan.amodio@aspectsecurity.com
| contributor_username1 = Dan_Amodio
| pamphlet_link =
| presentation_link =
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp-esapi-c
| project_road_map =
| links_url1 = http://code.google.com/p/owasp-esapi-c/
| links_name1 = ESAPI-C Google Code Project
| links_url2 = http://owasp-esapi-c.googlecode.com/svn/trunk/doc/html/index.html
| links_name2 = ESAPI-C Documentation
| release_1 =
| release_2 =
| release_3 =
| release_4 =

| project_about_page = Projects/OWASP ESAPI C Project
}}
<noinclude>[[Category: Project About]]</noinclude>