dbcve.org
Cpy Car Park ServerApplication · Gavazziautomation

CVE-2022-22522

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-28
Fix available
A fix is available. Upgrade to 2.8.3 / 8.5.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In 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 full 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 confidence

Carlo Gavazzi UWP3.0 and CPY Car Park Server contain hard-coded credentials embedded in the firmware that allow remote, unauthenticated attackers to gain full administrative access to the device. The vulnerability is exploitable over the network without any prior authentication.

MitigationImmediately update to patched versions if available, change default credentials, and implement network segmentation to limit exposure. If no patch exists, disable remote access and monitor for unauthorized access.

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
Cpy Car Park ServerApplication
Affected:< 2.8.3
Uwp 3.0 Monitoring Gateway And Controller FirmwareOperating system
Affected:< 8.5.0.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify UWP3.0 firmware version
    Access the device web interface or check via SNMP/sysinfo, or use the manufacturer's diagnostic tool to retrieve the current firmware version from the Monitoring Gateway And Controller
    Affected if The installed firmware version is lower than 8.5.0.3
  2. Identify CPY Car Park Server version
    Check the application version through the Car Park Server software interface, about screen, or check the installed software version on the host system
    Affected if The installed version is lower than 2.8.3
  3. Verify remote access configuration
    Check the device or server network settings to determine if remote HTTP/HTTPS access is enabled from untrusted networks
    Affected if Remote unauthenticated network access is permitted on the affected device
  4. Check network exposure
    Scan the network for accessible UWP3.0 or CPY Car Park Server instances on common ports (80, 443, 8080) and verify they are reachable from outside the trusted network segment
    Affected if The affected product is directly accessible from untrusted networks or the internet

You are affected if either the UWP3.0 firmware is below 8.5.0.3 or the CPY Car Park Server is below 2.8.3, AND the device is network accessible allowing remote unauthenticated attackers to use the hard-coded credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.8.3 / 8.5.0.3 or later
Fixed in 2.8.38.5.0.3
Interim mitigation

Immediately update to patched versions if available, change default credentials, and implement network segmentation to limit exposure. If no patch exists, disable remote access and monitor for unauthorized access.

Recommended fix High confidence

CPY Car Park Server: 2.8.3 | UWP 3.0 Monitoring Gateway And Controller Firmware: 8.5.0.3 or later

  1. 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. 2. For CPY Car Park Server: Determine current installed version (versions prior to 2.8.3 are affected)
  3. 3. For UWP 3.0 Monitoring Gateway And Controller: Determine current firmware version (versions prior to 8.5.0.3 are affected)
  4. 4. Obtain the fixed version from Carlo Gavazzi official channels (version 2.8.3 for CPY Car Park Server, version 8.5.0.3 or later for UWP 3.0)
  5. 5. Review upgrade procedures in official Carlo Gavazzi documentation
  6. 6. Schedule maintenance window for upgrade process
  7. 7. Apply upgrade to CPY Car Park Server to version 2.8.3
  8. 8. Apply firmware upgrade to UWP 3.0 devices to version 8.5.0.3 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cpy Car Park Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22522 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22522 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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