# Contract initializer permits unauthorized ownership or configuration

A reachable initialization path lets an ordinary actor establish or replace privileged state outside the intended deployment lifecycle.

**Candidate CWE:** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)

## Test hypothesis

In a faithful local deployment, compare intended initialization, a repeated initialization attempt and an ordinary actor’s attempt against the proxy or relevant instance. Check actual storage and roles.

## Evidence required

Proxy/implementation identity, initialization state, caller role, accepted transition and resulting protected capability.

## Rule out false positives

Initializing an unused implementation does not automatically compromise its proxy; prove how the changed state matters.

## Playbook and command references

- [Contract state: authorization, callbacks and accounting](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/smart-contract-state.html) — Turn protocol promises into explicit invariants and test realistic local operation sequences with independent accounting.
- [Object, function, and property authorization](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/authz-matrix.html) — Turn identities, tenants, objects, roles, and lifecycle transitions into a reproducible permission matrix.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Contract%20state%3A%20authorization%2C%20callbacks%20and%20accounting)

## Referenced by these target playbooks

[Web3 & protocols](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/web3.html) · [OSS & self-hosted](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/oss.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [OpenZeppelin Contracts 5.x proxies](https://docs.openzeppelin.com/contracts/5.x/api/proxy)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)