# Exposure of Resource to Wrong Sphere (CWE-668)

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

**Stack:** JavaScript

- Prevalence: 高 頻繁に悪用される
- Impact: クリティカル 1 件の重大度クリティカルなルール
- Prevention: 文書化済み 3 件の修正例

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

## Description

Resources should only be accessible to actors that are intended to use them. When resources are exposed to the wrong sphere (e.g., public instead of private), unauthorized actors can access sensitive data or functionality.

## Prevention

### JavaScript

Use ECMAScript private fields (#) for true runtime encapsulation instead of TypeScript's compile-time-only modifiers

## Warning Signs

- [HIGH] Access modifier bypass detected using .... Private/protected fields accessed through runtime mechanisms.

## Consequences

- アプリケーションデータの読み取り
- アプリケーションデータの変更
- 権限の取得

## Mitigations

- すべてのリソースに適切なアクセス制御を実装する
- 最小権限の原則を適用する
- リソースを信頼レベルごとに分離する

## Detection

- Total rules: 3
- Critical: 1
- Languages: yaml, typescript

## Rules by Language

### Typescript (1 rules)

- **TypeScript Access Modifier Bypass** [HIGH]: TypeScript private/protected modifiers are compile-time only. Bracket notation and
type assertions bypass them at runtime, exposing sensitive data like passwords and tokens.
  - Remediation: Use ECMAScript private fields (#) for true runtime encapsulation.

```typescript
class User {
  #password: string;

  constructor(password: string) {
    this.#password = password;
  }

  verifyPassword(input: string): boolean {
    return this.#password === input;
  }
}
```

Learn more: https://shoulder.dev/learn/typescript/cwe-668/access-modifier-bypass