Helix Core Server (P4D)
Approved changes feed: RSS · Atom
cpe:2.3:a:perforce:helix_core_server_(p4d):*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Perforce (b6773f0f-3a72-52f1-9555-ff325a988421) |
|---|---|
| Product | Helix Core Server (P4D) (0125de1c-c513-531c-9f3e-032b4ccd7d2b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-6043 |
vulnerable | 2026-06-03 15:27:54.682790 |
Insecure Default Configuration in P4 Server
P4 Server versions prior to 2026.1 are configured with insecure default settings that, when exposed to untrusted networks, allow unauthenticated attackers to create arbitrary user accounts, enumerate existing users, authenticate to accounts with no password set, and access depot contents via the built-in 'remote' user. These default settings, taken together, can lead to unauthorized access to source code repositories and other managed assets. The 2026.1 release, expected in May 2026, enforces secure-by-default configurations on upgrade and new installations
Published: 2026-04-24T11:02:50.723Z
Updated: 2026-04-28T12:12:01.630Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.