# Server-Side Request Forgery (SSRF) (CWE-918)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

- Prevalence: 中 覆盖 3 种语言
- Impact: 高 4 条严重级别为高的规则
- Prevention: 已记录 4 个修复示例

**OWASP:** Server-Side Request Forgery (A10:2021-Server-Side Request Forgery) - #10

## Description

By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls.

## Prevention

基于 4 条 Shoulder 检测规则的 Server-Side Request Forgery 预防策略。

### Go

Parse URL and validate host against domain allowlist

### JavaScript

Validate URLs against an allowlist of permitted domains before fetching

Validate URLs against domain allowlist before making requests

## Warning Signs

- [HIGH] user input flowing to HTTP client requests, enabling Server-Side Request Forgery attacks
- [HIGH] Server Action '...' has SSRF vulnerability: user input controls HTTP request URL
- [HIGH] user-controlled input flowing into HTTP request URLs in Server Actions
- [HIGH] user input flowing into HTTP request functions without URL validation
- [HIGH] user input controlling URLs in HTTP requests, allowing requests to
arbitrary destinations including 

## Consequences

- 读取应用程序数据
- 绕过保护机制
- 执行未授权命令

## Mitigations

- 对允许的目的地使用允许列表
- 禁用不必要的 URL 协议(file://、gopher://)
- 采用网络层级的分段隔离

## Detection

- Total rules: 4
- Languages: go, javascript, typescript, python

## Rules by Language

### Javascript (2 rules)

- **SSRF in Next.js Server Actions** [HIGH]: Detects user-controlled input flowing into HTTP request URLs in Server Actions.
  - Remediation: Validate and sanitize URLs before making HTTP requests. Use allowlists.
See remediation section for examples.
- **Server-Side Request Forgery via HTTP Requests** [HIGH]: Detects user input flowing into HTTP request functions without URL validation.
  - Remediation: Validate URLs against an allowlist of permitted domains before making requests.

```javascript
const url = new URL(userInput);
if (ALLOWED_DOMAINS.includes(url.hostname)) {
  axios.get(userInput);
}
```

Learn more: https://shoulder.dev/learn/javascript/cwe-918/ssrf

### Typescript (2 rules)

- **SSRF in Next.js Server Actions** [HIGH]: Detects user-controlled input flowing into HTTP request URLs in Server Actions.
  - Remediation: Validate and sanitize URLs before making HTTP requests. Use allowlists.
See remediation section for examples.
- **Server-Side Request Forgery via HTTP Requests** [HIGH]: Detects user input flowing into HTTP request functions without URL validation.
  - Remediation: Validate URLs against an allowlist of permitted domains before making requests.

```javascript
const url = new URL(userInput);
if (ALLOWED_DOMAINS.includes(url.hostname)) {
  axios.get(userInput);
}
```

Learn more: https://shoulder.dev/learn/javascript/cwe-918/ssrf

### Go (1 rules)

- **Server-Side Request Forgery (SSRF)** [HIGH]: Detects user input flowing to HTTP client requests, enabling Server-Side Request Forgery attacks.
  - Remediation: Validate URLs against an allowlist of permitted domains.

```go
allowed := map[string]bool{"api.example.com": true}
parsed, _ := url.Parse(targetURL)
if !allowed[parsed.Host] {
    return errors.New("domain not allowed")
}
```

Learn more: https://shoulder.dev/learn/go/cwe-918/ssrf

### Python (1 rules)

- **Server-Side Request Forgery (SSRF)** [HIGH]: Detects user input controlling URLs in HTTP requests, allowing requests to
arbitrary destinations including internal services and cloud metadata endpoints.
  - Remediation: Validate URLs against an allowlist of permitted domains.

```python
from urllib.parse import urlparse

ALLOWED_DOMAINS = {"api.github.com", "api.example.com"}
parsed = urlparse(user_url)
if parsed.hostname not in ALLOWED_DOMAINS:
    return "Invalid domain", 400
```

Learn more: https://shoulder.dev/learn/python/cwe-918/ssrf