Developers Coffee
Official@developerscoffee
Offers specialized remediation patterns for Java enterprise applications to eliminate common security vulnerabilities and enforce robust coding standards.
Agent Skills by Developers Coffee
Showing 54 vetted skills indexed across 2 GitHub repositories.
DevelopersCoffeetoleria-digital-twin
Extract architectural decisions, patterns, and technical debt from code repositories.
DevelopersCoffeecwe-89-sql-injection
Replace unsafe SQL string concatenation with parameterized statements in Java.
DevelopersCoffeecwe-367-race-condition-toctou
Remediate CWE-367 TOCTOU race conditions in Java code with atomic operations and synchronization.
DevelopersCoffeecwe-522-insufficiently-protected-credentials
Remediates CWE-522 vulnerabilities in Java code using Spring Security's BCrypt PasswordEncoder.
DevelopersCoffeecwe-311-non-encrypted-storage
Remediate CWE-311 vulnerabilities in Java code with AES-256-GCM encryption.
DevelopersCoffeecwe-307-brute-force-protection
Implement rate limiting and account lockout for Java authentication endpoints.
DevelopersCoffeecwe-552-files-accessible-externally
Implement authorization checks and filename sanitization for secure file serving in Spring Boot.
DevelopersCoffeecwe-501-trust-boundary-violation
Remediates CWE-501 trust boundary violations in Java by adding input validation and data source checks.
DevelopersCoffeecwe-613-insufficient-session-expiration
Remediates CWE-613 in Java Spring Security apps by configuring session timeouts.
DevelopersCoffeecwe-606-unchecked-loop-condition
Implement input validation limits for Java loop and sleep conditions vulnerable to CWE-606.
DevelopersCoffeecwe-328-weak-hash-algorithm
Replace MD5 and SHA1 with SHA-256, BCrypt, or Argon2 in Java code.
DevelopersCoffeecwe-377-insecure-temporary-file
Remediate CWE-377 insecure temporary file vulnerabilities in Java code.
DevelopersCoffeecwe-1333-redos
Replace vulnerable Java regex patterns with possessive quantifiers or atomic groups.
DevelopersCoffeecwe-284-improper-access-control
Implement Spring Security authorization checks to remediate CWE-284 vulnerabilities in Java.
DevelopersCoffeecwe-601-open-redirect
Remediate CWE-601 open redirect vulnerabilities in Java code.
DevelopersCoffeecwe-94-code-injection
Replace dynamic ScriptEngine.eval() calls with predefined safe operations in Java.
DevelopersCoffeecwe-833-deadlock
Remediate CWE-833 deadlock vulnerabilities in Java code with consistent lock ordering.
DevelopersCoffeecwe-295-insecure-tls-trust-manager
Remediates insecure TLS/SSL TrustManager and HostnameVerifier patterns in Java code.
DevelopersCoffeecwe-113-http-response-splitting
Sanitizes Java HTTP headers and cookies to prevent CWE-113 CRLF injection.
DevelopersCoffeecwe-327-weak-cryptography
Replace weak cryptographic algorithms with secure alternatives in Java code.
DevelopersCoffeecwe-362-race-condition
Remediate CWE-362 race conditions in Java using AtomicInteger or synchronized blocks.
DevelopersCoffeecwe-643-xpath-injection
Remediate CWE-643 XPath Injection vulnerabilities in Java code using secure XPath variable resolution.
DevelopersCoffeecwe-917-expression-language-injection
Replace StandardEvaluationContext with SimpleEvaluationContext to remediate CWE-917 in Java Spring SpEL.
DevelopersCoffeecwe-191-integer-underflow
Remediate CWE-191 integer underflow vulnerabilities in Java code.
Frequently Asked Questions About Developers Coffee
FAQPage SchemaWhat specific security tasks can I perform using these patterns?▼
You can remediate critical vulnerabilities including SQL injection, XSS, path traversal, and insecure credential storage. The patterns provide direct code-level replacements for unsafe Java operations, such as substituting weak hash algorithms with BCrypt or Argon2 and implementing secure session management.
Which technical personas benefit most from these security patterns?▼
These patterns are designed for Java backend engineers, security architects, and DevSecOps professionals. They provide actionable, drop-in code modifications for developers tasked with resolving static analysis findings or hardening enterprise applications against common OWASP and CWE-classified threats.
What are the prerequisites for implementing these security remediations?▼
Implementation requires a Java-based environment, specifically targeting Spring Boot and standard Java SE libraries. Developers should have access to their codebase to apply the provided logic, such as configuring Spring Security annotations or replacing standard library calls with secure alternatives like SecureRandom.