CVE-2022-28814
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 · uneditedCarlo Gavazzi UWP3.0 in multiple versions and CPY Car Park Server in Version 2.8.3 was discovered to be vulnerable to a relative path traversal vulnerability which enables remote attackers to read arbitrary files and gain full control 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 · high confidenceCarlo Gavazzi UWP3.0 and CPY Car Park Server contain a relative path traversal vulnerability enabling remote unauthenticated attackers to access arbitrary files on the filesystem via manipulated path references (e.g., ../ sequences). This can expose sensitive configuration files, credentials, and system files leading to full device compromise.
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< 2.8.3< 8.5.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Carlo Gavazzi productLocate and identify any Carlo Gavazzi software or firmware on the system, specifically Cpy Car Park Server or UWP 3.0 Monitoring Gateway. Check installed programs, services, or device firmware versions.Affected if Either Carlo Gavazzi Cpy Car Park Server or UWP 3.0 is present on the network or system
-
Check product version numberFor Cpy Car Park Server: check the installed software version in the application or service information. For UWP 3.0: check the firmware version via the device web interface, management console, or device documentation. Compare against affected versions: Cpy Car Park Server < 2.8.3 or UWP 3.0 < 8.5.0.3Affected if Version is below 2.8.3 for Cpy Car Park Server or below 8.5.0.3 for UWP 3.0
-
Verify file-serving functionality is exposedCheck if the web server or file-serving component of the affected product is accessible over the network. Attempt to access common paths such as the root web directory or look for HTTP/HTTPS services running on the device on typical ports (80, 443, or vendor-specific ports).Affected if The web interface or file-serving feature is accessible from the network without authentication
-
Test for path traversal vulnerabilityIf the web interface is accessible, attempt a controlled test request using ../ sequences (e.g., ../../../../etc/passwd or similar) to a known accessible file, using a method consistent with authorized security testing. Observe if the application returns files outside the intended directory.Affected if The application returns files from outside the intended web root directory when ../ sequences are used in requests
-
Review access logs for path traversal attemptsExamine server access logs, web server logs, or system logs for recent requests containing ../ patterns, directory traversal sequences, or unusual file access patterns targeting sensitive system files.Affected if Logs show path traversal attempts or successful unauthorized file access from external sources
You are affected if Carlo Gavazzi Cpy Car Park Server below version 2.8.3 or UWP 3.0 Monitoring Gateway below version 8.5.0.3 is installed and its web interface or file-serving functionality is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.8.38.5.0.3
Apply vendor-provided patches for UWP3.0 and CPY Car Park Server. If patches are unavailable, restrict network access to these services via firewall rules and disable unnecessary file-serving functionality as compensating controls.
Carlo Gavazzi UWP 3.0 firmware >= 8.5.0.3, CPY Car Park Server >= 2.8.3
- Identify the Carlo Gavazzi UWP 3.0 Monitoring Gateway And Controller device on your network
- Download firmware version 8.5.0.3 or later from the official Carlo Gavazzi vendor website
- Consult the device's firmware upgrade documentation for proper flashing procedure
- Upgrade the UWP 3.0 firmware to version 8.5.0.3 or later
- If running CPY Car Park Server, upgrade to version 2.8.3 or later
- After upgrading, verify the path traversal vulnerability is resolved by testing that directory traversal sequences (e.g., ../../../) are rejected or properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28814 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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