Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated.
Without limits on resource allocation, an attacker can consume all available resources, causing denial of service for legitimate users.
如何修复此漏洞
基于 3 条 Shoulder 检测规则的 Allocation Without Limits 预防策略。
Set size limits on body parser middleware to prevent memory exhaustion
- app.use(express.json()); - app.use(express.urlencoded({ extended: true })); + app.use(express.json({ limit: '100kb' })); + app.use(express.urlencoded({ extended: true, limit: '100kb' }));
Add 'take' limits to all relation includes to prevent unbounded data loading and resource exhaustion
import { PrismaClient } from '@prisma/client'; const prisma = new PrismaClient(); app.get('/api/users/:id', async (req, res) => { const user = await prisma.user.findUnique({ where: { id: req.params.id }, include: { - posts: true, // Could be thousands of posts - comments: true, // Could be tens of thousands + posts: { + take: 20, + orderBy: { createdAt: 'desc' }, + select: { id: true, title: true, createdAt: true }, + }, + comments: { + take: 50, + orderBy: { createdAt: 'desc' }, + }, } }); res.json(user); });
Add rate limiting to authentication and expensive API endpoints
from flask import Flask, request, jsonify - - @app.route('/api/login', methods=['POST']) + from flask_limiter import Limiter + from flask_limiter.util import get_remote_address + + limiter = Limiter(app=app, key_func=get_remote_address) + + @app.route('/api/login', methods=['POST']) + @limiter.limit("5 per minute") def login(): user = authenticate(request.json) return jsonify({'token': generate_token(user)})
查找代码中的漏洞
使用Shoulder扫描代码中的Allocation of Resources Without Limits or Throttling模式。 3 规则.
# Scan with Shoulder CLI npx @shoulderdev/cli trust --cwe=770 # Or scan entire project npx @shoulderdev/cli trust .
检测规则 (3)
代码审查中需要关注的内容
这些模式表明潜在的Allocation of Resources Without Limits or Throttling漏洞。在代码审查和安全审计中注意查找。
扫描你的代码库: Allocation of Resources Without Limits or Throttling
Shoulder CLI 在整个代码库中找到易受攻击的模式。