WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Vendor perforce✕
Overview 14 matches · 1 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
14matches 1in Waratek scope7.1% 0protected0.0% 0exploited0.0% 0CISA KEV0.0% 2public PoC14.3% 0EPSS ≥ 0.50.0%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 7.1% Outside Waratek scope 0 0.0% Not applicable 13 92.9% Withdrawn CVE 0 0.0%
Critical 0 0.0% High 0 0.0% Medium 14 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 14 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 2 14.3% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 12 85.7%
split by peak 6 / year
Not applicable: 13No exploit published: 1 Medium: 14 not blocked: 14 No public exploit: 12Working exploit published: 2
20082 Not applicable2 Medium2 not blocked2 Working exploit published1 No public exploit1 20090 20106 Not applicable6 Medium6 not blocked6 No public exploit6 20110 20120 20130 20140 20150 20160 20170 20181 No exploit published1 Medium1 not blocked1 No public exploit1 20190 20201 Not applicable1 Medium1 not blocked1 Working exploit published1 20211 Not applicable1 Medium1 not blocked1 No public exploit1 20221 Not applicable1 Medium1 not blocked1 No public exploit1 20230 20241 Not applicable1 Medium1 not blocked1 No public exploit1 20251 Not applicable1 Medium1 not blocked1 No public exploit1
200920112013201520172019202120232025
14 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2025-14591 Medium 2025-12-20 Not applicable No public exploit In Delphix Continuous Compliance version 2025.3.0 and later, following a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inaccurate parsing and leave personally identifiable information (PII) unmasked.
CVE-2024-5250 Medium 2024-07-30 Not applicable No public exploit In versions of Akana API Platform prior to 2024.1.0 overly verbose errors can be found in SAML integrations
CVE-2022-2394 Medium 2022-07-19 Not applicable No public exploit Puppet Bolt prior to version 3.24.0 will print sensitive parameters when planning a run resulting in them potentially being logged when run programmatically, such as via Puppet Enterprise.
CVE-2021-28973 Medium 2021-04-13 Not applicable No public exploit The XML Import functionality of the Administration console in Perforce Helix ALM 2020.3.1 Build 22 accepts XML input data that is parsed by insecurely configured software components, leading to XXE attacks.
CVE-2013-1410 Medium 2020-02-12 Not applicable Working exploit published Perforce P4web 2011.1 and 2012.1 has multiple XSS vulnerabilities
CVE-2018-1000147 Medium 2018-04-05 No exploit published No public exploit An exposure of sensitive information vulnerability exists in Jenkins Perforce Plugin version 1.3.36 and older in PerforcePasswordEncryptor.java that allows attackers with insufficient permission to obtain Perforce passwords configured in jobs to obtain them
CVE-2010-0935 Medium 2010-03-05 Not applicable No public exploit Perforce Server 2009.2 and earlier, when the protection table is empty, allows remote authenticated users to obtain super privileges via a "p4 protect" command.
CVE-2010-0933 Medium 2010-03-05 Not applicable No public exploit Directory traversal vulnerability in Perforce Server 2008.1 allows remote authenticated users to create arbitrary files via a .. (dot dot) in the argument to the "p4 add" command.
CVE-2010-0932 Medium 2010-03-05 Not applicable No public exploit The FTP server in Perforce Server 2008.1 allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a certain MKD command.
CVE-2010-0931 Medium 2010-03-05 Not applicable No public exploit The Perforce service (p4s.exe) in Perforce Server 2008.1 allows remote attackers to cause a denial of service (daemon crash) via crafted data, possibly involving a large sndbuf value.
CVE-2010-0930 Medium 2010-03-05 Not applicable No public exploit The Perforce service (p4s.exe) in Perforce Server 2008.1 allows remote attackers to cause a denial of service (infinite loop) via crafted data that includes a byte sequence of 0xdc, 0xff, 0xff, and 0xff immediately before the client protocol version number.
CVE-2010-0929 Medium 2010-03-05 Not applicable No public exploit The Perforce service (p4s.exe) in Perforce Server 2008.1 allows remote attackers to cause a denial of service (daemon crash) via crafted data beginning with a byte sequence of 0x4c, 0xb3, 0xff, 0xff, and 0xff.
CVE-2008-1303 Medium 2008-03-12 Not applicable Working exploit published The Perforce service (p4s.exe) in Perforce Server 2007.3/143793 and earlier allows remote attackers to cause a denial of service (daemon crash) via a missing parameter to the (1) dm-FaultFile, (2) dm-LazyCheck, (3) dm-ResolvedFile, (4) dm-OpenFile, (5) crypto, and possibly unspecified other commands, which triggers a NULL pointer dereference.
CVE-2008-1302 Medium 2008-03-12 Not applicable No public exploit The Perforce service (p4s.exe) in Perforce Server 2007.3/143793 and earlier allows remote attackers to cause a denial of service (daemon crash) via a (1) server-DiffFile or (2) server-ReleaseFile command with a large integer value, which is used in an array initialization calculation, and leads to invalid memory access.