dbcve.org
Cpy Car Park ServerApplication · Gavazziautomation

CVE-2022-28813

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
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 an SQL-injection to gain access to a volatile temporary database with the current states of 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 · moderate confidence

SQL injection vulnerability in Carlo Gavazzi UWP3.0 (multiple versions) and CPY Car Park Server v2.8.3 allows remote, unauthenticated attackers to access a volatile temporary database containing device state information.

MitigationApply vendor patches when available; as a temporary measure, implement input validation and consider deploying a WAF to block SQL injection attempts.

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 installed Carlo Gavazzi products
    Review system inventory or installed software list for 'Gavazziautomation Cpy Car Park Server' or 'UWP 3.0 Monitoring Gateway' components
    Affected if Either product is found on the system
  2. Check CPY Car Park Server version
    Locate the Car Park Server application and query its version information (typically via application UI, about dialog, or installed program properties)
    Affected if Version is present and less than 2.8.3
  3. Check UWP 3.0 firmware version
    Access the UWP3.0 device management interface or check firmware version through the monitoring gateway controller interface
    Affected if Firmware version is present and less than 8.5.0.3
  4. Verify network accessibility of the product
    Determine if the Carlo Gavazzi web interface or API service is exposed to network access (check firewall rules, NAT configurations, or port bindings for the product's management interface)
    Affected if The product's web interface is reachable from untrusted networks
  5. Identify temporary database exposure
    Since this vulnerability involves a temporary database containing device state information, check if the application's query parameters or endpoints can be manipulated to access this temporary storage without authentication
    Affected if Unauthenticated SQL queries can be submitted to the application

You are affected if you have CPY Car Park Server below version 2.8.3 or UWP 3.0 firmware below version 8.5.0.3 with their web interfaces network-accessible.

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 patches when available; as a temporary measure, implement input validation and consider deploying a WAF to block SQL injection attempts.

Recommended fix High confidence

CPY Car Park Server 2.8.3 or later | UWP3.0 Monitoring Gateway And Controller Firmware 8.5.0.3 or later

  1. Identify the exact version of Carlo Gavazzi UWP3.0 Monitoring Gateway And Controller Firmware currently installed
  2. Identify the exact version of CPY Car Park Server currently installed
  3. For UWP3.0 firmware: upgrade to version 8.5.0.3 or later
  4. For CPY Car Park Server: upgrade to version 2.8.3 or later
  5. Verify the upgrade was successful by checking the firmware/software version
  6. Test that the SQL injection vulnerability is no longer present

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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