CVE record · CVE-2023-5390

Path traversal in Honeywell ControlEdge UOC

CVSS 5.3 MediumEPSS 0.0057 · 47th percentile

Published by the CVE Program (CNA: Honeywell) at 31 Jan 2024, 17:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
Honeywell ControlEdge UOC
  • affected 520.2 to 520.2 TCU4, inclusive semver
  • affected 510.1 to 510.2 HF13, inclusive semver
  • affected 520.1 to 520.1 TCU4, inclusive semver
  • affected 511.1 to 511.5 TCU4 HF3, inclusive semver
Other versions: unaffected
Honeywell ControlEdge UOC
  • affected 520.2 to 520.2 TCU4, inclusive semver
  • affected 511.1 to 511.5 TCU4 HF3, inclusive semver
  • affected 520.1 to 520.1 TCU4, inclusive semver
Other versions: unaffected
Honeywell ControlEdge UOC
  • affected 520.2 to 520.2 TCU4, inclusive semver
  • affected 520.1 to 520.1 TCU4, inclusive semver
  • affected 520.2 TCU4 HFR2 to 511.5 TCU4 HF3, inclusive semver
Other versions: unaffected
Identifiers
CVE-2023-5390
CNA
Honeywell
Weakness (CWE)
CWE-36
Published
31 Jan 2024
Updated
29 May 2025

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (Honeywell)
  • CISA KEV Not listed.
  • EPSS 0.0057, the 47th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 31 Jan 2024. New records show when each source confirmed them.

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.