fix(security): mitigate path traversal vulnerability in S3RestoreJobFinished
This commit is contained in:
parent
648e111f10
commit
9930e1bc50
1 changed files with 0 additions and 159 deletions
|
|
@ -1,159 +0,0 @@
|
|||
# Security Fix: Path Traversal Vulnerability in S3RestoreJobFinished
|
||||
|
||||
## Vulnerability Summary
|
||||
|
||||
**CVE**: Not assigned
|
||||
**Severity**: High
|
||||
**Type**: Path Traversal / Directory Traversal
|
||||
**Affected Files**:
|
||||
- `app/Events/S3RestoreJobFinished.php`
|
||||
- `app/Events/RestoreJobFinished.php`
|
||||
|
||||
## Description
|
||||
|
||||
The original path validation in `S3RestoreJobFinished.php` (lines 70-87) used insufficient checks to prevent path traversal attacks:
|
||||
|
||||
```php
|
||||
// VULNERABLE CODE (Before fix)
|
||||
if (str($path)->startsWith('/tmp/') && !str($path)->contains('..') && strlen($path) > 5)
|
||||
```
|
||||
|
||||
### Attack Vector
|
||||
|
||||
An attacker could bypass this validation using:
|
||||
1. **Path Traversal**: `/tmp/../../../etc/passwd` - The `startsWith('/tmp/')` check passes, but the path escapes /tmp/
|
||||
2. **URL Encoding**: `/tmp/%2e%2e/etc/passwd` - URL-encoded `..` would bypass the `contains('..')` check
|
||||
3. **Null Byte Injection**: `/tmp/file.txt\0../../etc/passwd` - Null bytes could terminate string checks early
|
||||
|
||||
### Impact
|
||||
|
||||
If exploited, an attacker could:
|
||||
- Delete arbitrary files on the server or within Docker containers
|
||||
- Access sensitive system files
|
||||
- Potentially escalate privileges by removing protection mechanisms
|
||||
|
||||
## Solution
|
||||
|
||||
### 1. Created Secure Helper Function
|
||||
|
||||
Added `isSafeTmpPath()` function to `bootstrap/helpers/shared.php` that:
|
||||
|
||||
- **URL Decodes** input to catch encoded traversal attempts
|
||||
- **Normalizes paths** by removing redundant separators and relative references
|
||||
- **Validates structure** even for non-existent paths
|
||||
- **Resolves real paths** via `realpath()` for existing directories to catch symlink attacks
|
||||
- **Handles cross-platform** differences (e.g., macOS `/tmp` → `/private/tmp` symlink)
|
||||
|
||||
```php
|
||||
function isSafeTmpPath(?string $path): bool
|
||||
{
|
||||
// Multi-layered validation:
|
||||
// 1. URL decode to catch encoded attacks
|
||||
// 2. Check minimum length and /tmp/ prefix
|
||||
// 3. Reject paths containing '..' or null bytes
|
||||
// 4. Normalize path by removing //, /./, and rejecting /..
|
||||
// 5. Resolve real path for existing directories to catch symlinks
|
||||
// 6. Final verification that resolved path is within /tmp/
|
||||
}
|
||||
```
|
||||
|
||||
### 2. Updated Vulnerable Files
|
||||
|
||||
**S3RestoreJobFinished.php:**
|
||||
```php
|
||||
// BEFORE
|
||||
if (filled($serverTmpPath) && str($serverTmpPath)->startsWith('/tmp/') && !str($serverTmpPath)->contains('..') && strlen($serverTmpPath) > 5)
|
||||
|
||||
// AFTER
|
||||
if (isSafeTmpPath($serverTmpPath))
|
||||
```
|
||||
|
||||
**RestoreJobFinished.php:**
|
||||
```php
|
||||
// BEFORE
|
||||
if (str($tmpPath)->startsWith('/tmp/') && str($scriptPath)->startsWith('/tmp/') && !str($tmpPath)->contains('..') && !str($scriptPath)->contains('..') && strlen($tmpPath) > 5 && strlen($scriptPath) > 5)
|
||||
|
||||
// AFTER
|
||||
if (isSafeTmpPath($scriptPath)) { /* ... */ }
|
||||
if (isSafeTmpPath($tmpPath)) { /* ... */ }
|
||||
```
|
||||
|
||||
## Testing
|
||||
|
||||
Created comprehensive unit tests in:
|
||||
- `tests/Unit/PathTraversalSecurityTest.php` (16 tests, 47 assertions)
|
||||
- `tests/Unit/RestoreJobFinishedSecurityTest.php` (4 tests, 18 assertions)
|
||||
|
||||
### Test Coverage
|
||||
|
||||
✅ Null and empty input rejection
|
||||
✅ Minimum length validation
|
||||
✅ Valid /tmp/ paths acceptance
|
||||
✅ Path traversal with `..` rejection
|
||||
✅ Paths outside /tmp/ rejection
|
||||
✅ Double slash normalization
|
||||
✅ Relative directory reference handling
|
||||
✅ Trailing slash handling
|
||||
✅ URL-encoded traversal rejection
|
||||
✅ Mixed case path rejection
|
||||
✅ Null byte injection rejection
|
||||
✅ Non-existent path structural validation
|
||||
✅ Real path resolution for existing directories
|
||||
✅ Symlink-based traversal prevention
|
||||
✅ macOS /tmp → /private/tmp compatibility
|
||||
|
||||
All tests passing: ✅ 20 tests, 65 assertions
|
||||
|
||||
## Security Improvements
|
||||
|
||||
| Attack Vector | Before | After |
|
||||
|--------------|--------|-------|
|
||||
| `/tmp/../etc/passwd` | ❌ Vulnerable | ✅ Blocked |
|
||||
| `/tmp/%2e%2e/etc/passwd` | ❌ Vulnerable | ✅ Blocked (URL decoded) |
|
||||
| `/tmp/file\0../../etc/passwd` | ❌ Vulnerable | ✅ Blocked (null byte check) |
|
||||
| Symlink to /etc | ❌ Vulnerable | ✅ Blocked (realpath check) |
|
||||
| `/tmp//file.txt` | ❌ Rejected valid path | ✅ Accepted (normalized) |
|
||||
| `/tmp/./file.txt` | ❌ Rejected valid path | ✅ Accepted (normalized) |
|
||||
|
||||
## Files Modified
|
||||
|
||||
1. `bootstrap/helpers/shared.php` - Added `isSafeTmpPath()` function
|
||||
2. `app/Events/S3RestoreJobFinished.php` - Updated to use secure validation
|
||||
3. `app/Events/RestoreJobFinished.php` - Updated to use secure validation
|
||||
4. `tests/Unit/PathTraversalSecurityTest.php` - Comprehensive security tests
|
||||
5. `tests/Unit/RestoreJobFinishedSecurityTest.php` - Additional security tests
|
||||
|
||||
## Verification
|
||||
|
||||
Run the security tests:
|
||||
```bash
|
||||
./vendor/bin/pest tests/Unit/PathTraversalSecurityTest.php
|
||||
./vendor/bin/pest tests/Unit/RestoreJobFinishedSecurityTest.php
|
||||
```
|
||||
|
||||
All code formatted with Laravel Pint:
|
||||
```bash
|
||||
./vendor/bin/pint --dirty
|
||||
```
|
||||
|
||||
## Recommendations
|
||||
|
||||
1. **Code Review**: Conduct a security audit of other file operations in the codebase
|
||||
2. **Penetration Testing**: Test this fix in a staging environment with known attack vectors
|
||||
3. **Monitoring**: Add logging for rejected paths to detect attack attempts
|
||||
4. **Documentation**: Update security documentation to reference the `isSafeTmpPath()` helper for all future /tmp/ file operations
|
||||
|
||||
## Related Security Best Practices
|
||||
|
||||
- Always use dedicated path validation functions instead of ad-hoc string checks
|
||||
- Apply defense-in-depth: multiple validation layers
|
||||
- Normalize and decode input before validation
|
||||
- Resolve real paths to catch symlink attacks
|
||||
- Test security fixes with comprehensive attack vectors
|
||||
- Use whitelist validation (allowed paths) rather than blacklist (forbidden patterns)
|
||||
|
||||
---
|
||||
|
||||
**Date**: 2025-11-17
|
||||
**Author**: AI Security Fix
|
||||
**Severity**: High → Mitigated
|
||||
Loading…
Reference in a new issue