Secure coding

Secure Coding category emphasizes writing robust, secure software. Delve into best practices, vulnerabilities, and techniques ensuring safer applications and systems.

JNDI injection. Log4Shell case study

On December 10, 2021, Apache released a fix for CVE-2021-44228, a critical RCE vulnerability affecting Log4j that is being exploited… Read more

JNDI injection. JDBC

Preventing JNDI injection vulnerabilities by using a source code review is always a good idea. Read more

Secure secrets management in Docker containers. Part 1

Secure secrets management in Docker containers from the offensive point of view. With examples and demo scripts. Read more

Secure secrets management in Docker containers. Part 2

Secure secrets management in Docker containers from the offensive point of view. Secrets in memory. Secrets in build arguments Read more

Bash/zsh scripts. Part 3

Secure secrets management in Docker containers from the offensive point of view. Secrets in bash/zsh scripts. Secrets in logs. Read more

Git secret leaks

Secure secrets management in git from the offensive point of view. With examples and demo scripts. Read more

Obtain secrets from different sources

Obtain secrets from storage buckets, static landing pages and other static content with examples Read more

Avoiding injection vulnerabilities

Injection attacks refer to a broad class of attack vectors. In an injection attack, an attacker supplies untrusted input to… Read more

Avoiding XSS injection vulnerabilities

In this section, we'll describe some general principles for preventing cross-site scripting vulnerabilities and ways of using various common technologies Read more

Avoiding OS command injection

Every command call and dynamic code generation method is a ticking bomb and must be handled accordingly. Read more

Avoiding Templates injection

The best way to prevent server-side template injection is to not allow any users to modify or submit new templates. Read more

Avoiding other injections

Secure coding practices prescribe that spring expressions using dynamic values should be avoided. Read more