dbcve.org
Cpy Car Park ServerApplication · Gavazziautomation

CVE-2022-28816

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 the Sentilo Proxy is prone to reflected XSS which only affects the Sentilo service.

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

Reflected cross-site scripting (XSS) vulnerability in the Sentilo Proxy component of Carlo Gavazzi UWP3.0 (multiple versions) and CPY Car Park Server v2.8.3. The vulnerability allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in server responses.

MitigationImplement input validation and output encoding for all user-supplied data in the Sentilo Proxy. Since this is a vendor product, apply compensating controls such as WAF rules or network segmentation until vendor patches are available.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 product
    Locate and identify whether Carlo Gavazzi UWP3.0 Monitoring Gateway or CPY Car Park Server is deployed in your environment. Check product documentation, installed software lists, or system inventory for these product names.
    Affected if Either Carlo Gavazzi UWP3.0 Monitoring Gateway or CPY Car Park Server is installed
  2. Check installed firmware or software version
    Access the product admin interface, check system information page, or review installed software version. For UWP3.0, check the firmware version in the gateway settings. For CPY Car Park Server, check the application version in theAbout or System Info section.
    Affected if Version is below 8.5.0.3 for UWP3.0 firmware or below 2.8.3 for CPY Car Park Server
  3. Verify Sentilo Proxy component is enabled
    Access the product configuration settings and check whether the Sentilo Proxy component is enabled or configured. Look for Sentilo-related settings in the web interface or configuration files.
    Affected if Sentilo Proxy component is enabled or configured in the product
  4. Test for reflected XSS in web interface
    If Sentilo Proxy is accessible via web interface, observe whether user-supplied input in web requests (such as in URL parameters or form fields) is reflected back in server responses without sanitization. Use a manual test or browser developer tools to examine response content.
    Affected if User input is reflected in responses without output encoding, indicating the XSS vulnerability is present and exploitable

You are affected if you have UWP3.0 firmware below 8.5.0.3 or CPY Car Park Server below 2.8.3 with the Sentilo Proxy component enabled and 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

Implement input validation and output encoding for all user-supplied data in the Sentilo Proxy. Since this is a vendor product, apply compensating controls such as WAF rules or network segmentation until vendor patches are available.

Recommended fix High confidence

Cpy Car Park Server: 2.8.3 or later; UWP3.0: firmware 8.5.0.3 or later

  1. 1. Identify which Carlo Gavazzi product is deployed: Cpy Car Park Server or UWP3.0 Monitoring Gateway And Controller
  2. 2. For Cpy Car Park Server: determine current installed version (must be < 2.8.3)
  3. 3. For UWP3.0: determine current firmware version (must be < 8.5.0.3)
  4. 4. Obtain the fixed release from Carlo Gavazzi official channels or vendor support
  5. 5. For Cpy Car Park Server: upgrade to version 2.8.3 or later
  6. 6. For UWP3.0: upgrade firmware to version 8.5.0.3 or later
  7. 7. Verify the upgrade was successful by checking the product version
  8. 8. Test that the Sentilo Proxy service functions correctly post-upgrade

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-28816 — 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-28816 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