WECODE
Debugging
2023-10-26

Security Vulnerability Analyzer

Analyze code to identify, assess, and remediate security vulnerabilities using a multi-layered approach.

SCENARIO

You are a security expert with deep experience in application and system security. Your task is to identify, assess, and fix security vulnerabilities in the provided code, focusing on real-world attack scenarios and production risks.

LAYER 1: VULNERABILITY SCANNING

Conduct a security audit across the following areas:

  • Input validation and sanitization
  • Authentication mechanisms
  • Authorization and access control
  • Data protection and sensitive data handling

For each finding, identify:

  • Vulnerability type
  • Risk level
  • Possible attack vectors

LAYER 2: MITIGATION STRATEGY

For each identified vulnerability:

VULNERABILITY DETAILS:

  • Description of the issue
  • Potential impact if exploited
  • Exploitation difficulty

SOLUTION:

  • Required code changes
  • Additional security controls or safeguards
  • Validation and verification steps

VULNERABILITY #[n]:

TYPE: [Category] SEVERITY: [Critical / High / Medium / Low]

DESCRIPTION:

  • Attack scenario
  • Potential impact
  • Existing or missing protections

REMEDIATION:

  • Code fixes
  • Security measures
  • Testing and validation approach

PRINCIPLES TO FOLLOW:

  • Prioritize vulnerabilities based on real-world risk
  • Avoid theoretical issues with no practical exploit path
  • Follow secure coding best practices
  • Clearly explain tradeoffs between security, performance, and usability

INPUT:

Code: [Insert Code] Context: [Application type, environment, threat model if known]

More Debugging Prompts

Debugging
Hot

Fix Null Pointer Exception

A specialized prompt to help debug **NPEs** and identify the **root cause** of null references.

I am getting a NullPointerException in Java at this line: [Insert Code]. Can you trace where the null value might be coming from and suggest a production-grade fix?

Debugging
Hot

Fixing React Re-Render Issue

Debug why a React component is re-rendering too often and optimize performance.

Act as a senior software engineer with 20+ years of real-world experience. Review the following React component that is re-rendering more than it should. Assume the code is flawed until proven otherwise.

Walk through the component line by line and explain exactly why it re-renders, what is triggering each render, and which parts of the code are poorly designed or outright wrong. Identify unnecessary state updates, unstable references, misuse of hooks, or any architectural mistakes that lead to wasted renders.

Provide clear, opinionated fixes using best practices such as React.memo, useMemo, useCallback, or better state and component boundaries. If something should be refactored, say so directly and explain why.

Don't just patch the issue. Improve the code's performance, readability, and long-term maintainability as if this were production code you'd have to own. Ensure the final solution is idiomatic, efficient, and compatible with modern React standards.

Code to review: [Insert Code]

Debugging
Hot

Works on My Machine, Fails in Production

Analyze why code behaves differently across environments and fix the real root cause.

Act as a senior software engineer with over 20 years of production experience.

CONTEXT: The following code works locally but fails in another environment (staging or production). Assume this is an engineering failure, not bad luck.

YOUR TASK:

  • Walk through the code execution step by step
  • Identify environment-specific behavior, hidden dependencies, and incorrect assumptions
  • Call out fragile logic, poor error handling, reliance on local state, filesystem quirks, timing assumptions, and dependency differences

ANALYSIS REQUIREMENTS:

  • Provide a clear root-cause analysis supported by evidence from the code or execution flow
  • Explain what logs, signals, or checks would confirm the diagnosis before applying a fix

SOLUTION EXPECTATIONS:

  • Propose a robust, production-grade solution, not a band-aid
  • Refactor or redesign any part that would not survive real-world production conditions
  • Improve observability, error reporting, and defensive checks

VALIDATION:

  • Explain how the fix can be validated
  • Describe how it prevents similar failures in the future

INPUT: Code: [Insert Code] Failure context: [Local works / Production fails details]