phpIPAM < 1.8.2 Authentication Bypass via REST API Object Cache
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| phpipam | phpipam | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Phpipam | Phpipam |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.640% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:phpipam:phpipam:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Phpipam
Phpipam phpipam |
|
| Vendors & Products |
Phpipam
Phpipam phpipam |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to gain full API access by exploiting an insecure object cache keying mechanism. The cache is keyed by lookup value alone without including the searched column, enabling an entry written during an app_id lookup to satisfy a subsequent app_code lookup, allowing attackers to use the numeric database row identifier as an API token to read, write, and delete all IP address management records. | |
| Title | phpIPAM < 1.8.2 Authentication Bypass via REST API Object Cache | |
| Weaknesses | CWE-706 | |
| References |
| |
| Metrics |
cvssV3_1
|