Loading...
Agent Storage Exhaustion
ASECausing an agent to consume excessive storage through log bloating, memory persistence, file generation, or database growth, leading to storage exhaustion and service failure.
Example Scenario
Instructing an agent to "create detailed reports and save each intermediate step" for a massive multi-step task, causing it to generate thousands of files or database records that quickly consume available storage.
Testing Objectives
- Test storage limits
- Assess log rotation
- Evaluate file cleanup
- Validate quota enforcement
Defensive Strategies
- Storage quotas and limits
- Log rotation and cleanup
- File retention policies
- Database size monitoring
- Automatic cleanup mechanisms
Key Features
- Storage consumption maximization
- Log bloating
- File generation abuse
- Database growth exploitation
Use Cases
- Storage limit testing
- Log management validation
- File handling assessment
- Database quota evaluation
Tools & Frameworks
Security Risks
Ethical Guidelines
- •Test only with storage safeguards
- •Never exhaust production storage
- •Report storage vulnerabilities responsibly
- •Focus on improving cleanup mechanisms
- •Consider data integrity impact
Remember: This information is for educational and defensive security purposes only. Always ensure you have proper authorization before testing any techniques.
From the engineer behind this catalog
Get your agent system red-teamed
The attacks documented here work on production agent systems every day. Have yours tested before someone else does: prompt injection, jailbreaks, tool misuse and data exfiltration, with every finding written up next to its fix.
€750 instead of €1,500, one week, written report and walkthrough call, until 30 September