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

Dangerous eval function #47

Open
lidzhigaryaev opened this issue Jun 26, 2024 · 2 comments
Open

Dangerous eval function #47

lidzhigaryaev opened this issue Jun 26, 2024 · 2 comments

Comments

@lidzhigaryaev
Copy link

We're using OWASP ZAP pentests in our project and it recently gave us an alert saying that we use a dangerous eval JS function pointing to code in our bundle which leads to your library

Description A dangerous JS function seems to be in use that would leave the site vulnerable.
URL https://projectname/static/js/main.a2a68484.js
Evidence eval
Solution See the references for security advice on the use of these functions.
Tags WSTG-v42-CLNT-02
OWASP_2021_A04
CWE Id 749
Plugin Id 10110

image

Is there anything we can do about it? Thanks!

@lidzhigaryaev lidzhigaryaev changed the title Dangerous eval function Dangerous eval function Jun 26, 2024
@YYsuni
Copy link
Owner

YYsuni commented Jul 1, 2024

eval function is the easiest way for implementing the edit mode. I might be able to replace it with a more secure sdk.

@YYsuni
Copy link
Owner

YYsuni commented Jul 25, 2024

New canary released, eval has been replaced by JSON.parse.

blyme added a commit to blyme/jsonafy that referenced this issue Aug 10, 2024
blyme added a commit to blyme/jsonafy that referenced this issue Aug 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants