# Improper Access Control (CWE-284)

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

**Stack:** Go

- Prevalence: 高 頻繁に悪用される
- Impact: ハイ 3 件の重大度ハイのルール
- Prevention: 文書化済み 4 件の修正例

**OWASP:** Broken Access Control (A01:2021-Broken Access Control) - #1

## Description

Access control involves determining which subjects can access which objects. When access control is implemented incorrectly, it can lead to unauthorized access to sensitive data or functionality.

## Prevention

1 件の Shoulder 検出ルールに基づく Improper Access Control の予防策。

### Go

Validate tool inputs against strict schemas and use an allowlist for permitted tools

## Warning Signs

- [HIGH] Insecure plugin implementation: ...
- [HIGH] insecure plugin/function calling implementations in AI/LLM systems without proper validation

## Consequences

- アプリケーションデータの読み取り
- アプリケーションデータの変更
- 未承認コードの実行
- 権限の取得

## Mitigations

- すべてのリソースに適切なアクセス制御チェックを実装する
- 最小権限の原則を適用する
- アクセス制御は UI だけでなくサーバー側でも強制する

## Detection

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

## Rules by Language

### Go (1 rules)

- **LLM Insecure Plugin Design** [HIGH]: Detects insecure plugin/function calling implementations in AI/LLM systems without proper validation.
  - Remediation: Validate tool inputs against strict schemas and use an allowlist for permitted tools.

```go
if _, ok := toolRegistry[toolCall.Name]; !ok {
    return errors.New("unknown tool")
}
```

Learn more: https://shoulder.dev/learn/go/cwe-284/llm-insecure-plugin