CVE-2022-28812
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Carlo Gavazzi UWP3.0 in multiple versions and CPY Car Park Server in Version 2.8.3 a remote, unauthenticated attacker could make use of hard-coded credentials to gain SuperUser access to the device.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCarlo Gavazzi UWP3.0 and CPY Car Park Server contain hard-coded credentials embedded in the firmware/software that allow a remote, unauthenticated attacker to gain SuperUser access to the device, providing full administrative control over the affected system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.8.3< 8.5.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify deployed Carlo Gavazzi productsInventory your network for UWP3.0 Monitoring Gateway And Controller devices or CPY Car Park Server software installations. Check device labels, management interfaces, or software inventories for these product names.Affected if Either product is present in the environment
-
Check UWP3.0 firmware versionAccess the UWP3.0 device web interface or management console and locate the firmware version information, typically found under System Info, About, or Firmware sections. Compare the version number to the affected range (all versions before 8.5.0.3).Affected if Firmware version is lower than 8.5.0.3
-
Check CPY Car Park Server versionAccess the CPY Car Park Server management interface or check the installed software version through Programs and Features (Windows) or the application's About/Version info. Compare to the affected range (all versions before 2.8.3).Affected if Software version is lower than 2.8.3
-
Assess network exposureReview firewall rules, NAT configurations, and access control lists to determine if the UWP3.0 or CPY Car Park Server management interfaces are accessible from untrusted networks or the public internet.Affected if Device management interface is reachable from untrusted networks without VPN or authentication proxy
The environment is affected if Carlo Gavazzi UWP3.0 firmware below 8.5.0.3 or CPY Car Park Server below 2.8.3 is deployed and network-accessible, as the hard-coded SuperUser credentials can be exploited remotely without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.8.38.5.0.3
Immediately restrict network exposure of affected devices, change any default credentials if possible, and apply vendor-provided patches or firmware updates to remove hard-coded credentials.
CPY Car Park Server: 2.8.3 or later | UWP 3.0 Monitoring Gateway And Controller Firmware: 8.5.0.3 or later
- 1. Identify all deployed instances of Carlo Gavazzi CPY Car Park Server and UWP 3.0 Monitoring Gateway And Controller devices on the network
- 2. For CPY Car Park Server: Upgrade to version 2.8.3 or later
- 3. For UWP 3.0 Monitoring Gateway And Controller: Upgrade firmware to version 8.5.0.3 or later
- 4. After upgrading, verify that the hard-coded credentials have been removed by attempting to authenticate with the known hard-coded credentials (they should no longer work)
- 5. Ensure new, unique credentials are configured for SuperUser access
- 6. Document the upgrade in change management system
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28812 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data