Get Started
- CodeAnt AI
- Control Center
- Pull Request Review
- IDE
- Compliance
- Anti-Patterns
- Code Governance
- Infrastructure Security Database
- Application Security Database
- Apex
- Bash
- C
- Clojure
- Cpp
- Csharp
- Dockerfile
- Elixir
- Lang
- Best practice
- Correctness
- Correctness
- Security
- Command-injection
- Rce-code
- Rce-eex
- Sql-injection
- Traversal-file
- Traversal-send-download
- Traversal-send-file
- Unsafe-atom-interpolation
- Unsafe-binary-to-term
- Xss-content-type
- Xss-controller-html
- Xss-raw
- Phoenix
- Fingerprints
- Generic
- Go
- Html
- Java
- Javascript
- Json
- Kotlin
- Ocaml
- Php
- Problem-based-packs
- Python
- Ruby
- Rust
- Scala
- Solidity
- Swift
- Terraform
- Typescript
- Yaml
Unsafe-atom-interpolation
Unsafe atom interpolation
Atom values are appended to a global table but never removed. If input is user-controlled, dynamic instantiations such as :erlang.binary_to_atom can lead to possible memory leaks. Instead, use :erlang.binary_to_existing_atom or use the String.to_existing_atom function for untrusted user input.
Likelihood: MEDIUM
Confidence: MEDIUM
CWE:
- CWE-400: Uncontrolled Resource Consumption
OWASP:
- A05:2021 - Security Misconfiguration