AI Prompts for Preventing Security Vulnerabilities in Code

Please quote the exact SQL query generated in the last output that is vulnerable to SQL injection. Additionally, identify the specific input handling that led to this vulnerability and explain how it contributes to the risk. Format your response by clearly separating the quoted SQL query and the analysis of the input handling.

Please analyze the following function that handles user input in my project, specifically the one that processes SQL queries or file paths: [FUNCTION CODE]. Identify potential security vulnerabilities within this function, explain how they could be exploited, and suggest specific improvements to mitigate these risks. Format your response in a structured manner, detailing each vulnerability and the corresponding recommendation.

Please explain your understanding of my request to generate secure code. Identify the specific security measures you were expected to implement based on my previous instructions. Provide a detailed analysis of how these measures contribute to overall code security and any potential vulnerabilities that may arise if they are not addressed.

Identify the expected security behavior for user input handling in SQL queries in comparison to the actual output generated in the last execution. Please provide a detailed analysis that highlights any discrepancies between the expected and actual behaviors. Include specific examples of potential vulnerabilities that were identified and suggest improvements to align the actual behavior with security best practices.

Analyze the last generated code and identify any violated security constraints. For each violation, quote the exact rule or guideline that was not adhered to, and provide a brief explanation of the implications of each violation. Format your response as a list, clearly labeling each violation with its corresponding guideline.

Identify the SQL injection vulnerability in the function located at [FILE]:[LINE]. Provide a detailed explanation of why the current SQL query is susceptible to injection attacks. Then, rewrite the query to use parameterized queries for improved security. Finally, show me the diff of the changes made before applying them to the codebase.

Rewrite the input validation logic in the code located at [FILE] on line [LINE]. Ensure that the new logic properly sanitizes user input to prevent security vulnerabilities. Provide the revised code segment along with a detailed explanation of the changes made and the rationale behind them.

In the path handling function located at [FILE]:[LINE], please restrict the input to a predefined set of allowed paths. Provide the updated code that implements this restriction and confirm that it effectively prevents path traversal vulnerabilities. Additionally, include a brief explanation of how the changes improve security.

Please review the output rendering section in the file located at [FILE] on line [LINE]. Ensure that all user-generated content is properly encoded to prevent XSS vulnerabilities. Provide the updated code snippet along with a brief explanation of the changes made and how they enhance security.

Examine the dependencies listed in the package.json file for the project. Identify any security libraries that are missing and provide a list of these libraries. For each missing library, include instructions on how to add it to the package.json and confirm its installation. Finally, summarize the steps taken to ensure that all necessary security libraries are now included and properly installed.

Please run security tests on the modified code provided below: [CODE SNIPPET]. Confirm whether any SQL injection vulnerabilities have been resolved and provide a detailed report of the test results, including any remaining vulnerabilities, their severity, and recommended actions for further mitigation.

Please provide a detailed diff of the changes made to the vulnerable function in [FILE]. Ensure that you highlight all modifications and confirm that each identified vulnerability has been adequately addressed. Additionally, summarize any potential impacts these changes may have on the overall functionality of the code.

Please replay the original scenario that exposed the vulnerabilities in the code: [CODE SNIPPET]. Confirm whether the same security issues are still present by providing a detailed analysis of the results. Include any new findings or changes in behavior, and summarize the effectiveness of the resolution in preventing these vulnerabilities.

Please analyze the modified function for user input handling and identify any potential edge cases that may not be securely managed. Provide a detailed report that includes a list of the edge cases tested, the results of each test, and any vulnerabilities found. Additionally, suggest specific improvements or changes that can be made to ensure secure handling of all identified edge cases.

Please verify the state of [FILE] after the recent changes have been made. Check to ensure that it no longer contains any vulnerabilities related to SQL injection, XSS, or path traversal. Provide a detailed report outlining any remaining issues, along with recommendations for further improvements if necessary.

Before any deployment step, please verify that all SQL queries in this project use parameterized statements and that all user inputs are properly sanitized. If any of these checks fail, stop the deployment process and alert the developer immediately. Ensure that no deployment occurs without passing these essential security checks to prevent potential vulnerabilities.

Generate a project convention message that emphasizes the importance of input validation and sanitization for security compliance. The message should state: "All user inputs must be validated and sanitized before processing." Additionally, include a specific format for the validation, such as "[VALIDATION FUNCTION]", and provide a brief explanation of why this practice is crucial for preventing security vulnerabilities. Ensure the message is clear and actionable for the development team.

Please add a code comment in [FILE] that clearly states the importance of preventing XSS attacks. The comment should read: "Ensure all user-generated content is encoded before rendering to prevent XSS attacks. Use [ENCODING FUNCTION] for compliance." This comment should be placed above the relevant code section to serve as a reminder for developers working on this file.

Generate a reminder message for the project that emphasizes the importance of including security libraries in the package.json file. The message should state: "Always check for and include security libraries in package.json. Use [SECURITY LIBRARY] for SQL protection and [XSS LIBRARY] for output encoding." Ensure the message is clear and concise, and suggest a review process for regularly updating these libraries to maintain security standards.

Create a self-check request for security compliance that verifies the following before generating code: all SQL queries must be parameterized, user inputs must be sanitized, and outputs must be encoded. If any of these security constraints are not met, the process should stop and an alert should be sent to the developer. Format the output as a clear checklist that can be easily referenced during the coding process.