Project Harbor harbor

Name: Project Harbor harbor
Brand: Project Harbor

productRU

A product tracked in the threat graph; the vulnerabilities below are known to affect it.

KEV-listed

by severity

5critical18high12medium0low

updated 2026-10-27

vulnerabilities (35)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2023-38545US	critical9.8	78.7% (100th)	Exploit	no fix	2023-10-18	≤ 2.7.0
CVE-2023-38039US	high7.5	56.4% (99th)	Exploit	no fix	2023-09-15	≤ 2.7.0
CVE-2007-4559US	medium6.8	27.1% (98th)	Exploit	no fix	2007-08-28	≤ 2.7.0
CVE-2023-24329US	high7.5	20.5% (97th)	Exploit	no fix	2023-02-17	≤ 2.7.0
CVE-2022-37434US	critical9.8	19.2% (97th)	Exploit	no fix	2022-08-05	≤ 1.10.13
CVE-2023-4813US	medium5.9	2.22% (83rd)	Exploit	no fix	2023-09-12	≤ 2.7.0
CVE-2023-2650US	medium6.5	75.4% (100th)	—	no fix	2023-05-30	≤ 2.7.0
CVE-2022-4450US	high7.5	28.6% (98th)	—	no fix	2023-02-08	≤ 2.7.0
CVE-2022-43551US	high7.5OT elevated	16.6% (97th)	—	no fix	2022-12-23	≤ 2.7.0
CVE-2022-42898US	high8.8	6.86% (94th)	—	no fix	2022-12-25	≤ 2.7.0
CVE-2023-3446US	medium5.3	6.53% (94th)	—	no fix	2023-07-19	≤ 2.7.0
CVE-2020-10735US	high7.5	4.49% (91st)	—	no fix	2022-09-09	≤ 2.7.0
CVE-2023-5678US	medium5.3	4.46% (91st)	—	no fix	2023-11-06	≤ 2.7.0
CVE-2023-45853US	critical9.8	3.45% (89th)	—	no fix	2023-10-14	≤ 2.7.0
CVE-2023-3817US	medium5.3	3.05% (87th)	—	no fix	2023-07-31	≤ 2.7.0
CVE-2022-40897US	medium5.9	2.63% (85th)	—	no fix	2022-12-23	≤ 2.7.0
CVE-2023-27043US	medium5.3	2.53% (85th)	—	no fix	2023-04-19	≤ 2.7.0
CVE-2023-27534US	high8.8	2.44% (84th)	—	no fix	2023-03-30	≤ 2.7.0
CVE-2023-27533US	high8.8	2.16% (82nd)	—	no fix	2023-03-30	≤ 2.7.0
CVE-2023-0401US	high7.5	1.85% (79th)	—	no fix	2023-02-08	≤ 2.7.0
CVE-2023-0217US	high7.5	1.85% (79th)	—	no fix	2023-02-08	≤ 2.7.0
CVE-2019-16919US	high7.5OT elevated	1.71% (77th)	—	no fix	2019-10-18	2 versions
CVE-2023-5156US	high7.5	1.63% (76th)	—	no fix	2023-09-25	≤ 2.7.0
CVE-2023-4806US	medium5.9	1.61% (76th)	—	no fix	2023-09-18	≤ 2.7.0
CVE-2023-4807US	high7.8	1.58% (75th)	—	no fix	2023-09-08	≤ 2.7.0
CVE-2022-24963US	critical9.8	1.47% (74th)	—	no fix	2023-01-31	≤ 2.7.0
CVE-2022-1304US	high7.8	1.47% (73rd)	—	no fix	2022-04-14	≤ 2.7.0
CVE-2023-7104US	high7.3	1.46% (73rd)	—	no fix	2023-12-29	≤ 2.7.0
CVE-2019-19025US	high8.8	1.02% (63rd)	—	no fix	2020-03-20	1.7.0 → 1.8.6
CVE-2023-23914US	critical9.1OT elevated	0.90% (59th)	—	no fix	2023-02-23	≤ 2.7.0
CVE-2023-0767US	high8.8	0.82% (57th)	—	no fix	2023-06-02	≤ 2.7.0
CVE-2023-40217US	medium5.3	0.80% (56th)	—	no fix	2023-08-25	≤ 2.7.0
CVE-2023-2975US	medium5.3	0.62% (50th)	—	no fix	2023-07-14	≤ 2.7.0
CVE-2022-46908US	high7.3OT elevated	0.45% (39th)	—	no fix	2022-12-12	≤ 2.7.0
CVE-2021-33294US	medium5.5	0.33% (26th)	—	no fix	2023-07-18	≤ 2.7.0

weaknesses (8)

The flaw types (CWEs) most of these CVEs share.

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer4 CVEs
CWE-122Heap-based Buffer Overflow3 CVEs
CWE-190Integer Overflow or Wraparound3 CVEs
CWE-20Improper Input Validation3 CVEs
CWE-606Unchecked Input for Loop Condition3 CVEs
CWE-787Out-of-bounds Write3 CVEs
CWE-1333Inefficient Regular Expression Complexity2 CVEs
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')2 CVEs

sources (1)

Which sources assert this record, and when.

RUBDU (FSTEC Data Security Threats Database)35 CVEs

scry

Products carry known vulnerabilities once they are exposed to the internet. See what is exposed on your perimeter with a free passive scan.

Free scan