Products

Solutions

Resources

/

/

Struts OGNL Console Enabled

Struts OGNL Console Enabled

Detection of Struts OGNL console enabled misconfiguration, which can lead to remote code execution vulnerabilities.

Security Misconfiguration (SM)

The Struts OGNL Console Enabled test identifies a security misconfiguration where the OGNL (Object-Graph Navigation Language) console in Struts framework is accessible. By modifying the URL and appending "struts/webconsole.html?debug=console," the test checks if the OGNL console is enabled and accessible. Enabling the OGNL console can lead to remote code execution vulnerabilities, allowing attackers to execute arbitrary code on the server. This misconfiguration falls under the Security Misconfiguration category with a low severity level. Disabling the OGNL console is essential to prevent potential remote code execution and enhance application security.

The Struts OGNL Console Enabled test identifies a security misconfiguration where the OGNL (Object-Graph Navigation Language) console in Struts framework is accessible. By modifying the URL and appending "struts/webconsole.html?debug=console," the test checks if the OGNL console is enabled and accessible. Enabling the OGNL console can lead to remote code execution vulnerabilities, allowing attackers to execute arbitrary code on the server. This misconfiguration falls under the Security Misconfiguration category with a low severity level. Disabling the OGNL console is essential to prevent potential remote code execution and enhance application security.

Impact of the vulnerability

Impact of the vulnerability

Enabling Struts OGNL console exposes the application to remote code execution, allowing attackers to execute arbitrary code on the server.

Enabling Struts OGNL console exposes the application to remote code execution, allowing attackers to execute arbitrary code on the server.

How this template works

APIs Selection

The template uses API selection filters to specify the criteria for selecting the APIs to be tested. In this case, the filters include checking the response code to be between 200 and 299 and extracting the URL from the response.

Execute request

The template uses the execute section to define the type of request to be executed. In this case, it is a single request. The request is modified by appending "/struts/webconsole.html?debug=console" to the extracted URL.

Validation

The template uses the validate section to define the validation criteria for the response. It checks that the response code is 200 and that the response payload contains the string "Welcome to the OGNL console!".

Frequently asked questions

What is the purpose of the Struts OGNL Console Enabled test

What is the purpose of the Struts OGNL Console Enabled test

What is the purpose of the Struts OGNL Console Enabled test

How does the test check if the OGNL console is enabled and accessible

How does the test check if the OGNL console is enabled and accessible

How does the test check if the OGNL console is enabled and accessible

What are the potential risks of enabling the Struts OGNL console

What are the potential risks of enabling the Struts OGNL console

What are the potential risks of enabling the Struts OGNL console

What category and severity level does this test fall under

What category and severity level does this test fall under

What category and severity level does this test fall under

How can disabling the OGNL console enhance application security

How can disabling the OGNL console enhance application security

How can disabling the OGNL console enhance application security

Are there any references or resources available for further information on this test

Are there any references or resources available for further information on this test

Are there any references or resources available for further information on this test

Loved by security teams!

Loved by security teams!

Product Hunt Badge

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Loom Company logo

Security team,

Loom

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Loom Company logo

Security team,

Loom

"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "

Rippling Company logo

Security team,

Rippling

Suggest API security tests

Suggest API security tests

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.