-
Notifications
You must be signed in to change notification settings - Fork 23
Modernization of CDR #53
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
base: release/16.0
Are you sure you want to change the base?
Conversation
This appears to be AI-generated and contains multiple potential SQL injection errors. |
@chrsmj Can you give me an example just to check? It's just to see if claude is able to fixe it. |
No I am not going to debug your AI generated code. |
Well. As you like. |
Are there any unit tests being added ? |
Hey @danardf , just a quick pointer on the SQL injection topic. Check out how $_REQUEST['sort'] is used to build the ORDER BY clause in the new getCdrData function. Directly using request parameters in that part of a query is a common risk. A whitelist for allowed column names is usually the safest approach there. Hope that's a helpful starting point! |
@mrpbueno hi |
Interestingly, the current Cdr.class.php has the same SQL injection issues, AI didn't seem to create those Franck just used what already existed. So kudos you just discovered existing SQL injection issues in the CDR module. |
Fixe SQL injections Add unit test
Fixe SQL injections Fixe SQL injections Add unit test
…to modernization-cdr
I think it's fixed now |
Hi |
@kguptasangoma Hi |
Hi @danardf did not get chance to look into this one. Needs to kick off the QA also. Thanks |
@kguptasangoma Ok update me asap. please. |
May be we can ask community help also to test the PR. |
As you want. |
I modernized this old module which was ugly for a long time ago. Now it looks better.