Improper Handling of Exceptional Conditions
The product does not handle or incorrectly handles an exceptional condition.
When exceptional conditions are not properly handled, the product may enter an undefined state, crash, or expose sensitive information. This can lead to denial of service, information disclosure, or unexpected behavior.
이 취약점을 수정하는 방법
4개의 Shoulder 탐지 규칙을 기반으로 한 Improper Handling of Exceptional Conditions 예방 전략.
Always check error return values before using other results
result, err := process() - if result == nil { - return + if err != nil { + return fmt.Errorf("process failed: %w", err) } useResult(result)
Use finally blocks to release resources (connections, file handles) on all code paths
- const connection = await pool.getConnection(); - const result = await connection.query(sql); - connection.release(); - return result; + let connection; + try { + connection = await pool.getConnection(); + const result = await connection.query(sql); + return result; + } finally { + if (connection) await connection.release(); + }
Return error responses when security checks fail instead of continuing execution
- from flask import request - - @app.route('/api/admin') - def admin_data(): - try: - user = authenticate(request.headers.get('Authorization')) - except Exception: - pass # Auth failed but continues + from flask import request, abort + + @app.route('/api/admin') + def admin_data(): + try: + user = authenticate(request.headers.get('Authorization')) + except Exception: + abort(403) return {'admin_data': get_sensitive_data()}
Wrap database, file, network, and API operations in try/except with proper logging
- import requests - - def fetch_data(url): - response = requests.get(url) - return response.json() + import logging + import requests + + logger = logging.getLogger(__name__) + + def fetch_data(url): + try: + response = requests.get(url, timeout=5) + response.raise_for_status() + return response.json() + except requests.RequestException as e: + logger.error(f"Request failed: {e}") + return None
코드에서 취약점 찾기
Shoulder를 사용하여 코드에서 Improper Handling of Exceptional Conditions 패턴을 스캔하세요. 4 규칙.
# Scan with Shoulder CLI npx @shoulderdev/cli trust --cwe=755 # Or scan entire project npx @shoulderdev/cli trust .
탐지 규칙 (4)
코드 리뷰에서 주의할 점
이 패턴은 잠재적인 Improper Handling of Exceptional Conditions 취약점을 나타냅니다. 코드 리뷰와 보안 감사 중에 찾아보세요.
코드베이스를 스캔하세요: Improper Handling of Exceptional Conditions
Shoulder CLI는 전체 코드베이스에서 취약한 패턴을 찾아냅니다.