Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API7:2023 Security Misconfiguration - Misleading example #79

Closed
ynvb opened this issue Mar 5, 2023 · 3 comments
Closed

API7:2023 Security Misconfiguration - Misleading example #79

ynvb opened this issue Mar 5, 2023 · 3 comments
Labels
2023RC pending community feedback Waiting to be reviewed by the community

Comments

@ynvb
Copy link

ynvb commented Mar 5, 2023

Scenario #1 - This category shows a JNDI injection issue.
I don't believe a JNDI injection is a good example of a "security misconfiguration" issue. sure, sometimes there might be an unnecessary JNDI feature within some specific functionality, and it's really better to turn it off. However, in many other cases, the JNDI functionality is required, and cannot be simply removed. In this case, the best mitigation should follow the line of "Input Sanitization", Usage of "Parameterized Queries", and so on.
This is a much better example for Injection use cases (which is partially described in API10:2023 - Unsafe Consumption of APIs)

@ErezYalon
Copy link
Member

I tend to agree. We should find a different scenario.
Let's open it to the community to come up with better examples.

@ErezYalon ErezYalon added the pending community feedback Waiting to be reviewed by the community label Mar 23, 2023
@gavjl
Copy link
Contributor

gavjl commented Mar 23, 2023

How about something CORS related? Already mentioned a couple of times in that entry too

@LaurentCB
Copy link

Are bad Keys Management based scenarios (for cloud services access for instance) in the scope ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2023RC pending community feedback Waiting to be reviewed by the community
Projects
None yet
Development

No branches or pull requests

5 participants