dbcve.org
Cpy Car Park ServerApplication · Gavazziautomation

CVE-2022-22523

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
An improper authentication vulnerability exists in the Carlo Gavazzi UWP3.0 in multiple versions and CPY Car Park Server in Version 2.8.3 Web-App which allows an authentication bypass to the context of an unauthorised user if free-access is disabled.

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 · moderate confidence

An improper authentication vulnerability in Carlo Gavazzi UWP3.0 and CPY Car Park Server v2.8.3 allows an unauthenticated attacker to bypass authentication controls when free-access is disabled, potentially gaining unauthorized access to the application and its functions.

MitigationApply vendor-provided patches or firmware updates for UWP3.0 and CPY Car Park Server. If no patch is available, restrict network exposure and implement additional access controls such as VPN or IP whitelisting to limit attack surface.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 if CPY Car Park Server is installed
    Locate the application in the system (typically installed as a Windows service or application) and check its version through the application About screen, installed programs list, or service properties
    Affected if Version is installed and less than 2.8.3
  2. Identify if UWP3.0 firmware is in use
    Access the device admin interface, web console, or system information page of the Carlo Gavazzi monitoring gateway or controller device and note the firmware version
    Affected if Firmware version is present and less than 8.5.0.3
  3. Check authentication configuration in CPY Car Park Server
    Open the application configuration settings, admin panel, or settings menu and locate the authentication or access control settings to verify whether free-access is disabled
    Affected if Free-access setting is explicitly disabled (set to off or denied)
  4. Check authentication configuration in UWP3.0 device
    Access the device web interface or management console and navigate to access control, authentication, or security settings to verify the free-access configuration status
    Affected if Free-access setting is explicitly disabled (set to off or denied)

A system is affected if it runs CPY Car Park Server below version 2.8.3 or UWP3.0 firmware below 8.5.0.3 AND has free-access disabled, allowing potential unauthenticated bypass of authentication controls.

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

Apply vendor-provided patches or firmware updates for UWP3.0 and CPY Car Park Server. If no patch is available, restrict network exposure and implement additional access controls such as VPN or IP whitelisting to limit attack surface.

Recommended fix Moderate confidence

CPY Car Park Server: upgrade to version 2.8.3 or later; UWP 3.0 Monitoring Gateway And Controller: upgrade to firmware version 8.5.0.3 or later

  1. Obtain the Carlo Gavazzi UWP3.0 firmware version 8.5.0.3 or later from the vendor (Carlo Gavazzi)
  2. Obtain the Carlo Gavazzi CPY Car Park Server version 2.8.3 or later from the vendor
  3. Back up all current configurations and data before applying updates
  4. Apply the firmware update to UWP 3.0 Monitoring Gateway And Controller devices
  5. Apply the software update to CPY Car Park Server
  6. Verify that free-access functionality is properly configured after update
  7. Confirm the authentication bypass vulnerability is resolved by testing access controls

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

Fix this in Cpy Car Park Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22523 — 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-22523 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