dbcve.org
Cpy Car Park ServerApplication · Gavazziautomation

CVE-2022-28811

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 utilize an improper input validation on an API-submitted parameter to execute arbitrary OS commands.

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

A command injection vulnerability exists in Carlo Gavazzi UWP3.0 (multiple versions) and CPY Car Park Server v2.8.3 where improper input validation on an API-submitted parameter allows remote, unauthenticated attackers to execute arbitrary OS commands. This is a classic OS command injection flaw in the web/API interface of these embedded devices and parking management software.

MitigationApply vendor patches or firmware updates for UWP3.0 and CPY Car Park Server when available. If no patch exists, implement compensating controls such as network segmentation to restrict access to the affected interfaces, and deploy WAF rules to detect and block command 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
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 the Carlo Gavazzi product
    Determine if the system is running either UWP 3.0 Monitoring Gateway And Controller or CPY Car Park Server. Check the product name displayed in the web interface, system information page, or software inventory.
    Affected if The product is not one of the two affected products (UWP3.0 or CPY Car Park Server), then this CVE does not apply.
  2. Determine the installed version
    Locate the version number in the product's web interface (typically under About, System Info, or Settings), or check the firmware/software version reported by the device. For UWP3.0, this is the firmware version. For CPY Car Park Server, this is the application version.
    Affected if Unable to determine the version, treat as potentially affected and investigate further.
  3. Compare version against vulnerable ranges
    Compare the installed version to the affected ranges: CPY Car Park Server versions below 2.8.3 are vulnerable; UWP 3.0 firmware versions below 8.5.0.3 are vulnerable.
    Affected if The installed version falls within the vulnerable range (CPY < 2.8.3 or UWP3.0 firmware < 8.5.0.3), then the system is affected by this CVE.
  4. Verify API interface accessibility
    Check if the product's web API endpoint is accessible from the network. This vulnerability exploits the API parameter input. Determine if the device HTTP/HTTPS ports are exposed to untrusted networks.
    Affected if The API interface is accessible remotely without authentication, exploitation is possible.
  5. Review access logs for suspicious API calls
    Examine server, device, or proxy logs for API requests containing shell metacharacters (such as ;, |, &&, $, backticks, or command substitution patterns) in parameter values. Look for unexpected execution attempts.

The system is affected if it runs Carlo Gavazzi UWP3.0 firmware below 8.5.0.3 or CPY Car Park Server below version 2.8.3, and the API interface is 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 or firmware updates for UWP3.0 and CPY Car Park Server when available. If no patch exists, implement compensating controls such as network segmentation to restrict access to the affected interfaces, and deploy WAF rules to detect and block command injection attempts.

Recommended fix High confidence

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

  1. Upgrade CPY Car Park Server to version 2.8.3 or later
  2. Upgrade UWP 3.0 Monitoring Gateway And Controller Firmware to version 8.5.0.3 or later
  3. After upgrading, verify that the API input validation is properly sanitizing parameters to prevent command injection

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

Fix this in Cpy Car Park Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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