Overview 155 matches · 24 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
155matches
24in Waratek scope15.5%
2protected1.3%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
2
1.3%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
22
14.2%
Outside Waratek scope
0
0.0%
Not applicable
131
84.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
2
1.3%
partly blocked
0
0.0%
not blocked
153
98.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
155
100.0%
split by
peak 34 / year
20041
Not applicable1
Medium1
not blocked1
No public exploit1
20050
20060
20070
20080
20090
20100
20110
20120
20130
20140
20150
201611
No exploit published1
Not applicable10
Critical1
High7
Medium3
not blocked11
No public exploit11
201734
Protected by Waratek1
No exploit published13
Not applicable20
Critical8
High13
Medium12
Low1
blocked by ARMR today1
not blocked33
No public exploit34
201816
Protected by Waratek1
No exploit published6
Not applicable9
Critical5
High8
Medium3
blocked by ARMR today1
not blocked15
No public exploit16
20198
No exploit published1
Not applicable7
High5
Medium3
not blocked8
No public exploit8
20201
Not applicable1
High1
not blocked1
No public exploit1
20212
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20229
Not applicable9
Critical4
High2
Medium3
not blocked9
No public exploit9
202313
Not applicable13
High4
Medium9
not blocked13
No public exploit13
202424
Not applicable24
Critical7
High7
Medium10
not blocked24
No public exploit24
202524
Not applicable24
Critical5
High9
Medium8
Low2
not blocked24
No public exploit24
202612
No exploit published1
Not applicable11
Critical3
High1
Medium2
Low6
not blocked12
No public exploit12
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-85917 | High | 2026-09-17 | Not applicable | No public exploit | Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network. |
| CVE-2026-85889 | Critical | 2026-09-17 | Not applicable | No public exploit | Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network. |
| CVE-2026-56583 | Low | 2026-07-21 | Not applicable | No public exploit | HCL MyCloud was affected with Concurrent Login Vulnerability. It may increase the risk of unauthorized access, session hijacking, and account misuse. |
| CVE-2026-56582 | Low | 2026-07-21 | Not applicable | No public exploit | HCL MyCloud was affected by the SSL/TLS LUCKY13 Vulnerability. An attacker may exploit this vulnerability to decrypt sensitive information through a TLS/SSL padding oracle attack. |
| CVE-2026-56581 | Low | 2026-07-21 | Not applicable | No public exploit | HCL MyCloud was affected with Cookie Attribute Path Not Set. It may increase the risk of unauthorized access to session data or authentication tokens. |
| CVE-2026-56580 | Low | 2026-07-21 | Not applicable | No public exploit | HCL MyCloud was affected by Using Components with Known Vulnerability ( IIS Server ). It may allow attackers to exploit publicly disclosed weaknesses and compromise the system. |
| CVE-2026-56579 | Low | 2026-07-21 | Not applicable | No public exploit | HCL MyCloud was affected with License Key Revealed in HTTP Response. It may enable attackers to misuse the exposed information and compromise the application's security. |
| CVE-2026-56578 | Low | 2026-07-21 | Not applicable | No public exploit | HCL MyCloud was affected by Server Version Disclosure. It may help attackers identify and exploit known vulnerabilities affecting the disclosed software versions. |
| CVE-2026-56577 | Medium | 2026-07-21 | Not applicable | No public exploit | HCL MyCloud was affected with Weak Password Policy. It may increase the risk of account compromise through brute-force or credential-based attacks. |
| CVE-2026-35435 | Critical | 2026-05-07 | Not applicable | No public exploit | Improper access control in Azure AI Foundry M365 published agents allows an unauthorized attacker to elevate privileges over a network. |
| CVE-2026-32213 | Critical | 2026-04-03 | Not applicable | No public exploit | Improper authorization in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network. |
| CVE-2026-22723 | Medium | 2026-03-05 | No exploit published | No public exploit | Inappropriate user token revocation due to a logic error in the token revocation endpoint implementation in Cloudfoundry UAA v77.30.0 to v78.7.0 and in Cloudfoundry Deployment v48.7.0 to v54.10.0. |
| CVE-2025-31954 | Medium | 2025-11-05 | Not applicable | No public exploit | HCL iAutomate v6.5.1 and v6.5.2 is susceptible to a sensitive information disclosure. An HTTP GET method is used to process a request and includes sensitive information in the query string of that request. An attacker could potentially access information or resources they were not intended to see. |
| CVE-2025-52658 | Medium | 2025-10-03 | Not applicable | No public exploit | HCL MyXalytics is affected by the use of vulnerable/outdated versions which can expose the application to known security risks that could be exploited. |
| CVE-2025-52656 | High | 2025-10-03 | Not applicable | No public exploit | HCL MyXalytics: 6.6. is affected by Mass Assignment vulnerability. Mass Assignment occurs when user input is automatically bound to application objects without proper validation or access controls, potentially allowing unauthorized modification of sensitive fields. |
| CVE-2025-52654 | Medium | 2025-10-03 | Not applicable | No public exploit | HCL MyXalytics v6.6 is affected by an HTML Injection. This issue occurs when untrusted input is included in the output without proper handling, potentially allowing unauthorized content injection and manipulation. |
| CVE-2025-52653 | High | 2025-10-03 | Not applicable | No public exploit | HCL MyXalytics product is affected by Cross Site Scripting vulnerability in the web application. This can allow the execution of unauthorized scripts, potentially resulting in unauthorized actions or access. |
| CVE-2025-31955 | High | 2025-07-24 | Not applicable | No public exploit | HCL iAutomate is affected by a sensitive data exposure vulnerability. This issue may allow unauthorized access to sensitive information within the system. |
| CVE-2025-31953 | High | 2025-07-24 | Not applicable | No public exploit | HCL iAutomate includes hardcoded credentials which may result in potential exposure of confidential data if intercepted or accessed by unauthorized parties. |
| CVE-2025-31952 | High | 2025-07-24 | Not applicable | No public exploit | HCL iAutomate is affected by an insufficient session expiration. This allows tokens to remain valid indefinitely unless manually revoked, increasing the risk of unauthorized access. |
| CVE-2024-42178 | High | 2025-04-17 | Not applicable | No public exploit | HCL MyXalytics is affected by a failure to restrict URL access vulnerability. Unauthenticated users might gain unauthorized access to potentially confidential information, creating a risk of misuse, manipulation, or unauthorized distribution. |
| CVE-2024-42177 | Medium | 2025-04-17 | Not applicable | No public exploit | HCL MyXalytics is affected by SSL∕TLS Protocol affected with BREACH & LUCKY13 vulnerabilities. Attackers can exploit the weakness in the ciphers to intercept and decrypt encrypted data, steal sensitive information, or inject malicious code into the system. |
| CVE-2024-42176 | High | 2025-03-19 | Not applicable | No public exploit | HCL MyXalytics is affected by concurrent login vulnerability. A concurrent login vulnerability occurs when simultaneous active sessions are allowed for a single credential allowing an attacker to potentially obtain access to a user's account or sensitive information. |
| CVE-2024-30150 | Critical | 2025-02-25 | Not applicable | No public exploit | HCL MyCloud is affected by Improper Access Control - an unauthenticated privilege escalation vulnerability which may lead to information disclosure and potential for Server-Side Request Forgery (SSRF) and Denial of Service(DOS) attacks from unauthenticated users. |
| CVE-2024-42207 | Medium | 2025-02-05 | Not applicable | No public exploit | HCL iAutomate is affected by a session fixation vulnerability. An attacker could hijack a victim's session ID from their authenticated session. |
| CVE-2024-42181 | High | 2025-01-12 | Not applicable | No public exploit | HCL MyXalytics is affected by a cleartext transmission of sensitive information vulnerability. The application transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. |
| CVE-2024-42180 | Critical | 2025-01-12 | Not applicable | No public exploit | HCL MyXalytics is affected by a malicious file upload vulnerability. The application accepts invalid file uploads, including incorrect content types, double extensions, null bytes, and special characters, allowing attackers to upload and execute malicious files. |
| CVE-2024-42179 | Low | 2025-01-12 | Not applicable | No public exploit | HCL MyXalytics is affected by sensitive information disclosure vulnerability. The HTTP response header exposes the Microsoft-HTTP API∕2.0 as the server's name & version. |
| CVE-2024-42175 | Critical | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by a weak input validation vulnerability. The application accepts special characters and there is no length validation. This can lead to security vulnerabilities like SQL injection, XSS, and buffer overflow. |
| CVE-2024-42174 | Low | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by username enumeration vulnerability. This allows a malicious user to perform enumeration of application users, and therefore compile a list of valid usernames. |
| CVE-2024-42173 | Medium | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by an improper password policy implementation vulnerability. Weak passwords and lack of account lockout policies allow attackers to guess or brute-force passwords if the username is known. |
| CVE-2024-42172 | Critical | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by broken authentication. It allows attackers to compromise keys, passwords, and session tokens, potentially leading to identity theft and system control. This vulnerability arises from poor configuration, logic errors, or software bugs and can affect any application with access control, including databases, network infrastructure, and web applications. |
| CVE-2024-42171 | Medium | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by a session fixation vulnerability. Cyber-criminals can exploit this by sending crafted URLs with a session token to access the victim's login session. |
| CVE-2024-42170 | Medium | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by a session fixation vulnerability. Cyber-criminals can exploit this by sending crafted URLs with a session token to access the victim's login session. |
| CVE-2024-42169 | High | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by insecure direct object references. It occurs due to missing access control checks, which fail to verify whether a user should be allowed to access specific data. |
| CVE-2024-42168 | Critical | 2025-01-11 | Not applicable | No public exploit | HCL MyXalytics is affected by out-of-band resource load (HTTP) vulnerability. An attacker can deploy a web server that returns malicious content, and then induce the application to retrieve and process that content. |
| CVE-2024-30135 | High | 2024-06-28 | Not applicable | No public exploit | HCL DRYiCE AEX is potentially impacted by disclosure of sensitive information in the mobile application when a snapshot is taken. |
| CVE-2024-30111 | High | 2024-06-28 | Not applicable | No public exploit | HCL DRYiCE AEX product is impacted by Missing Root Detection vulnerability in the mobile application. The mobile app can be installed in the rooted device due to which malicious users can gain unauthorized access to the rooted devices, compromising security and potentially leading to data breaches or other malicious activities. |
| CVE-2024-30110 | Critical | 2024-06-28 | Not applicable | No public exploit | HCL DRYiCE AEX product is impacted by lack of input validation vulnerability in a particular web application. A malicious script can be injected into a system which can cause the system to behave in unexpected ways. |
| CVE-2024-30109 | Medium | 2024-06-28 | Not applicable | No public exploit | HCL DRYiCE AEX is impacted by a lack of clickjacking protection in the AEX web application. An attacker can use multiple transparent or opaque layers to trick a user into clicking on a button or link on another page than the one intended. |
| CVE-2024-4818 | Medium | 2024-05-14 | Not applicable | No public exploit | A vulnerability was found in Campcodes Online Laundry Management System 1.0 and classified as problematic. This issue affects some unknown processing of the file /index.php. The manipulation of the argument page leads to file inclusion. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-263939. |
| CVE-2024-4817 | Medium | 2024-05-14 | Not applicable | No public exploit | A vulnerability has been found in Campcodes Online Laundry Management System 1.0 and classified as critical. This vulnerability affects unknown code of the file manage_user.php of the component HTTP Request Parameter Handler. The manipulation of the argument id leads to improper control of resource identifiers. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-263938 is the identifier assigned to this vulnerability. |
| CVE-2024-4797 | Medium | 2024-05-14 | Not applicable | No public exploit | A vulnerability was found in Campcodes Online Laundry Management System 1.0. It has been declared as problematic. This vulnerability affects unknown code of the file /ajax.php. The manipulation of the argument name/customer_name/username leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-263896. |
| CVE-2024-4795 | Medium | 2024-05-14 | Not applicable | No public exploit | A vulnerability was found in Campcodes Online Laundry Management System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /manage_user.php. The manipulation of the argument id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-263894 is the identifier assigned to this vulnerability. |
| CVE-2024-4792 | Medium | 2024-05-14 | Not applicable | No public exploit | A vulnerability, which was classified as critical, has been found in Campcodes Online Laundry Management System 1.0. This issue affects some unknown processing of the file /admin_class.php. The manipulation of the argument id/delete_category/delete_inv/delete_laundry/delete_supply/delete_user/login/save_inv/save_user leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-263891. |
| CVE-2023-50347 | Critical | 2024-04-10 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by an insecure SQL interface vulnerability, potentially giving an attacker the ability to execute custom SQL queries. A malicious user can run arbitrary SQL commands including changing system configuration. |
| CVE-2024-3464 | Critical | 2024-04-08 | Not applicable | No public exploit | A vulnerability was found in SourceCodester Laundry Management System 1.0 and classified as critical. This issue affects the function laporan_filter of the file /application/controller/Pelanggan.php. The manipulation of the argument jeniskelamin leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-259745 was assigned to this vulnerability. |
| CVE-2023-34061 | High | 2024-01-12 | Not applicable | No public exploit | Cloud Foundry routing release versions from v0.163.0 to v0.283.0 are vulnerable to a DOS attack. An unauthenticated attacker can use this vulnerability to force route pruning and therefore degrade the service availability of the Cloud Foundry deployment. |
| CVE-2023-50351 | Critical | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by the use of an insecure key rotation mechanism which can allow an attacker to compromise the confidentiality or integrity of data. |
| CVE-2023-50350 | High | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by the use of a broken cryptographic algorithm for encryption, potentially giving an attacker ability to decrypt sensitive information. |
| CVE-2023-50348 | Medium | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by an improper error handling vulnerability. The application returns detailed error messages that can provide an attacker with insight into the application, system, etc. |
| CVE-2023-50346 | Medium | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by an information disclosure vulnerability. Certain endpoints within the application disclose detailed file information. |
| CVE-2023-50345 | Medium | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by an Open Redirect vulnerability which could allow an attacker to redirect users to malicious sites, potentially leading to phishing attacks or other security threats. |
| CVE-2023-50344 | Medium | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by improper access control (Unauthenticated File Download) vulnerability. An unauthenticated user can download certain files. |
| CVE-2023-50343 | High | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by an Improper Access Control (Controller APIs) vulnerability. Certain API endpoints are accessible to Customer Admin Users that can allow access to sensitive information about other users. |
| CVE-2023-50342 | High | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by an Insecure Direct Object Reference (IDOR) vulnerability. A user can obtain certain details about another user as a result of improper access control. |
| CVE-2023-50341 | High | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by Improper Access Control (Obsolete web pages) vulnerability. Discovery of outdated and accessible web pages, reflects a "Missing Access Control" vulnerability, which could lead to inadvertent exposure of sensitive information and/or exposing a vulnerable endpoint. |
| CVE-2023-45724 | Critical | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics product is impacted by unauthenticated file upload vulnerability. The web application permits the upload of a certain file without requiring user authentication. |
| CVE-2023-45723 | Critical | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by path traversal vulnerability which allows file upload capability. Certain endpoints permit users to manipulate the path (including the file name) where these files are stored on the server. |
| CVE-2023-45722 | Critical | 2024-01-03 | Not applicable | No public exploit | HCL DRYiCE MyXalytics is impacted by path traversal arbitrary file read vulnerability because it uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory. The product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Potential exploits can completely disrupt or take over the application. |
| CVE-2023-23347 | High | 2023-08-09 | Not applicable | No public exploit | HCL DRYiCE iAutomate is affected by the use of a broken cryptographic algorithm. An attacker can potentially compromise the confidentiality and integrity of sensitive information. |
| CVE-2023-23346 | High | 2023-08-09 | Not applicable | No public exploit | HCL DRYiCE MyCloud is affected by the use of a broken cryptographic algorithm. An attacker can potentially compromise the confidentiality and integrity of sensitive information. |
| CVE-2023-30952 | Medium | 2023-08-03 | Not applicable | No public exploit | A security defect was discovered in Foundry Issues that enabled users to create convincing phishing links by editing the request sent when creating an Issue. This defect was resolved in Frontend release 6.228.0 . |
| CVE-2023-30950 | Medium | 2023-08-03 | Not applicable | No public exploit | The foundry campaigns service was found to be vulnerable to an unauthenticated information disclosure in a rest endpoint |
| CVE-2023-30963 | Medium | 2023-07-10 | Not applicable | No public exploit | A security defect was discovered in Foundry Frontend which enabled users to perform Stored XSS attacks in Slate if Foundry's CSP were to be bypassed. This defect was resolved with the release of Foundry Frontend 6.229.0. The service was rolled out to all affected Foundry instances. No further intervention is required. |
| CVE-2023-30960 | Medium | 2023-07-10 | Not applicable | No public exploit | A security defect was discovered in Foundry job-tracker that enabled users to query metadata related to builds on resources they did not have access to. This defect was resolved with the release of job-tracker 4.645.0. The service was rolled out to all affected Foundry instances. No further intervention is required. |
| CVE-2023-30956 | Medium | 2023-07-10 | Not applicable | No public exploit | A security defect was identified in Foundry Comments that enabled a user to discover the contents of an attachment submitted to another comment if they knew the internal UUID of the target attachment. This defect was resolved with the release of Foundry Comments 2.267.0. |
| CVE-2023-22835 | High | 2023-07-10 | Not applicable | No public exploit | A security defect was identified that enabled a user of Foundry Issues to perform a Denial of Service attack by submitting malformed data in an Issue that caused loss of frontend functionality to all issue participants. This defect was resolved with the release of Foundry Issues 2.510.0 and Foundry Frontend 6.228.0. |
| CVE-2023-30955 | Medium | 2023-06-29 | Not applicable | No public exploit | A security defect was identified in Foundry workspace-server that enabled a user to bypass an authorization check and view settings related to 'Developer Mode'. This enabled users with insufficient privilege the ability to view and interact with Developer Mode settings in a limited capacity. A fix was deployed with workspace-server 7.7.0. |
| CVE-2023-30946 | Medium | 2023-06-29 | Not applicable | No public exploit | A security defect was identified in Foundry Issues. If a user was added to an issue on a resource that they did not have access to and consequently could not see, they could query Foundry's Notification API and receive metadata about the issue including the RID of the issue, severity, internal UUID of the author, and the user-defined title of the issue. |
| CVE-2023-20885 | Medium | 2023-06-16 | Not applicable | No public exploit | Vulnerability in Cloud Foundry Notifications, Cloud Foundry SMB-volume release, Cloud FOundry cf-nfs-volume release.This issue affects Notifications: All versions prior to 63; SMB-volume release: All versions prior to 3.1.19; cf-nfs-volume release: 5.0.X versions prior to 5.0.27, 7.1.X versions prior to 7.1.19. |
| CVE-2023-30948 | Medium | 2023-06-06 | Not applicable | No public exploit | A security defect in Foundry's Comments functionality resulted in the retrieval of attachments to comments not being gated by additional authorization checks. This could enable an authenticated user to inject a prior discovered attachment UUID into other arbitrary comments to discover it's content. This defect was fixed in Foundry Comments 2.249.0, and a patch was rolled out to affected Foundry environments. No further intervention is required at this time. |
| CVE-2023-22833 | High | 2023-06-06 | Not applicable | No public exploit | Palantir Foundry deployments running Lime2 versions between 2.519.0 and 2.532.0 were vulnerable a bug that allowed authenticated users within a Foundry organization to bypass discretionary or mandatory access controls under certain circumstances. |
| CVE-2022-27895 | High | 2022-11-15 | Not applicable | No public exploit | Information Exposure Through Log Files vulnerability discovered in Foundry when logs were captured using an underlying library known as Build2. This issue was present in versions earlier than 1.785.0. Upgrade to Build2 version 1.785.0 or greater. |
| CVE-2022-27896 | High | 2022-11-14 | Not applicable | No public exploit | Information Exposure Through Log Files vulnerability discovered in Foundry Code-Workbooks where the endpoint backing that console was generating service log records of any Python code being run. These service logs included the Foundry token that represents the Code-Workbooks Python console. Upgrade to Code-Workbooks version 4.461.0. This issue affects Palantir Foundry Code-Workbooks version 4.144 to version 4.460.0 and is resolved in 4.461.0. |
| CVE-2022-31691 | Critical | 2022-11-04 | Not applicable | No public exploit | Spring Tools 4 for Eclipse version 4.16.0 and below as well as VSCode extensions such as Spring Boot Tools, Concourse CI Pipeline Editor, Bosh Editor and Cloudfoundry Manifest YML Support version 1.39.0 and below all use Snakeyaml library for YAML editing support. This library allows for some special syntax in the YAML that under certain circumstances allows for potentially harmful remote code execution by the attacker. |
| CVE-2022-27894 | Medium | 2022-11-04 | Not applicable | No public exploit | The Foundry Blobster service was found to have a cross-site scripting (XSS) vulnerability that could have allowed an attacker with access to Foundry to launch attacks against other users. This vulnerability is resolved in Blobster 3.228.0. |
| CVE-2022-31066 | Medium | 2022-06-14 | Not applicable | No public exploit | EdgeX Foundry is an open source project for building a common open framework for Internet of Things edge computing. Prior to version 2.1.1, the /api/v2/config endpoint exposes message bus credentials to local unauthenticated users. In security-enabled mode, message bus credentials are supposed to be kept in the EdgeX secret store and require authentication to access. This vulnerability bypasses the access controls on message bus credentials when running in security-enabled mode. (No credentials are required when running in security-disabled mode.) As a result, attackers could intercept data or inject fake data into the EdgeX message bus. Users should upgrade to EdgeXFoundry Kamakura release (2.2.0) or to the June 2022 EdgeXFoundry LTS Jakarta release (2.1.1) to receive a patch. More information about which go modules, docker containers, and snaps contain patches is available in the GitHub Security Advisory. There are currently no known workarounds for this issue. |
| CVE-2022-27889 | Critical | 2022-06-14 | Not applicable | No public exploit | The Multipass service was found to have code paths that could be abused to cause a denial of service for authentication or authorization operations. A malicious attacker could perform an application-level denial of service attack, potentially causing authentication and/or authorization operations to fail for the duration of the attack. This could lead to performance degradation or login failures for customer Palantir Foundry environments. This vulnerability is resolved in Multipass 3.647.0. This issue affects: Palantir Foundry Multipass versions prior to 3.647.0. |
| CVE-2022-28452 | Critical | 2022-04-29 | Not applicable | No public exploit | Red Planet Laundry Management System 1.0 is vulnerable to SQL Injection. |
| CVE-2022-27888 | Medium | 2022-04-26 | Not applicable | No public exploit | Foundry Issues service versions 2.244.0 to 2.249.0 was found to be logging in a manner that captured sensitive information (session tokens). This issue was fixed in 2.249.1. |
| CVE-2021-45003 | Critical | 2022-01-10 | Not applicable | No public exploit | Laundry Booking Management System 1.0 (Latest) and previous versions are affected by a remote code execution (RCE) vulnerability in profile.php through the "image" parameter that can execute a webshell payload. |
| CVE-2021-41278 | Medium | 2021-11-19 | Not applicable | No public exploit | Functions SDK for EdgeX is meant to provide all the plumbing necessary for developers to get started in processing/transforming/exporting data out of the EdgeX IoT platform. In affected versions broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. The app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline. No decrypt function is provided. Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation. Version v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place. The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation. As the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected. Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new "aes256" transform. |
| CVE-2021-32753 | High | 2021-07-09 | Not applicable | No public exploit | EdgeX Foundry is an open source project for building a common open framework for internet-of-things edge computing. A vulnerability exists in the Edinburgh, Fuji, Geneva, and Hanoi versions of the software. When the EdgeX API gateway is configured for OAuth2 authentication and a proxy user is created, the client_id and client_secret required to obtain an OAuth2 authentication token are set to the username of the proxy user. A remote network attacker can then perform a dictionary-based password attack on the OAuth2 token endpoint of the API gateway to obtain an OAuth2 authentication token and use that token to make authenticated calls to EdgeX microservices from an untrusted network. OAuth2 is the default authentication method in EdgeX Edinburgh release. The default authentication method was changed to JWT in Fuji and later releases. Users should upgrade to the EdgeX Ireland release to obtain the fix. The OAuth2 authentication method is disabled in Ireland release. If unable to upgrade and OAuth2 authentication is required, users should create OAuth2 users directly using the Kong admin API and forgo the use of the `security-proxy-setup` tool to create OAuth2 users. |
| CVE-2020-5399 | High | 2020-02-12 | Not applicable | No public exploit | Cloud Foundry CredHub, versions prior to 2.5.10, connects to a MySQL database without TLS even when configured to use TLS. A malicious user with access to the network between CredHub and its MySQL database may eavesdrop on database connections and thereby gain unauthorized access to CredHub and other components. |
| CVE-2019-11283 | High | 2019-10-23 | Not applicable | No public exploit | Cloud Foundry SMB Volume, versions prior to v2.0.3, accidentally outputs sensitive information to the logs. A remote user with access to the SMB Volume logs can discover the username and password for volumes that have been recently created, allowing the user to take control of the SMB Volume. |
| CVE-2019-11282 | Medium | 2019-10-23 | Not applicable | No public exploit | Cloud Foundry UAA, versions prior to v74.3.0, contains an endpoint that is vulnerable to SCIM injection attack. A remote authenticated malicious user with scim.invite scope can craft a request with malicious content which can leak information about users of the UAA. |
| CVE-2019-3800 | High | 2019-08-05 | Not applicable | No public exploit | CF CLI version prior to v6.45.0 (bosh release version 1.16.0) writes the client id and secret to its config file when the user authenticates with --client-credentials flag. A local authenticated malicious user with access to the CF CLI config file can act as that client, who is the owner of the leaked credentials. |
| CVE-2019-11270 | High | 2019-08-05 | Not applicable | No public exploit | Cloud Foundry UAA versions prior to v73.4.0 contain a vulnerability where a malicious client possessing the 'clients.write' authority or scope can bypass the restrictions imposed on clients created via 'clients.write' and create clients with arbitrary scopes that the creator does not possess. |
| CVE-2019-3794 | Medium | 2019-07-18 | Not applicable | No public exploit | Cloud Foundry UAA, versions prior to v73.4.0, does not set an X-FRAME-OPTIONS header on various endpoints. A remote user can perform clickjacking attacks on UAA's frontend sites. |
| CVE-2019-11268 | Medium | 2019-07-11 | Not applicable | No public exploit | Cloud Foundry UAA version prior to 73.3.0, contain endpoints that contains improper escaping. An authenticated malicious user with basic read privileges for one identity zone can extend those reading privileges to all other identity zones and obtain private information on users, clients, and groups in all other identity zones. |
| CVE-2019-3787 | High | 2019-06-19 | Not applicable | No public exploit | Cloud Foundry UAA, versions prior to 73.0.0, falls back to appending “unknown.org” to a user's email address when one is not provided and the user name does not contain an @ character. This domain is held by a private company, which leads to attack vectors including password recovery emails sent to a potentially fraudulent address. This would allow the attacker to gain complete control of the user's account. |
| CVE-2019-1003025 | High | 2019-02-20 | No exploit published | No public exploit | A exposure of sensitive information vulnerability exists in Jenkins Cloud Foundry Plugin 2.3.1 and earlier in AbstractCloudFoundryPushDescriptor.java that allows attackers with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2018-15754 | High | 2018-12-13 | Not applicable | No public exploit | Cloud Foundry UAA, versions 60 prior to 66.0, contain an authorization logic error. In environments with multiple identity providers that contain accounts across identity providers with the same username, a remote authenticated user with access to one of these accounts may be able to obtain a token for an account of the same username in the other identity provider. |
| CVE-2018-15797 | High | 2018-12-05 | Not applicable | No public exploit | Cloud Foundry NFS volume release, 1.2.x prior to 1.2.5, 1.5.x prior to 1.5.4, 1.7.x prior to 1.7.3, logs the cf admin username and password when running the nfsbrokerpush BOSH deploy errand. A remote authenticated user with access to BOSH can obtain the admin credentials for the Cloud Foundry Platform through the logs of the NFS volume deploy errand. |
| CVE-2018-15761 | Critical | 2018-11-19 | No exploit published | No public exploit | Cloud Foundry UAA release, versions prior to v64.0, and UAA, versions prior to 4.23.0, contains a validation error which allows for privilege escalation. A remote authenticated user may modify the url and content of a consent page to gain a token with arbitrary scopes that escalates their privileges. |
| CVE-2018-1264 | Critical | 2018-10-05 | Not applicable | No public exploit | Cloud Foundry Log Cache, versions prior to 1.1.1, logs its UAA client secret on startup as part of its envstruct report. A remote attacker who has gained access to the Log Cache VM can read this secret, gaining all privileges held by the Log Cache UAA client. In the worst case, if this client is an admin, the attacker would gain complete control over the Foundation. |
| CVE-2018-11082 | Critical | 2018-10-05 | Not applicable | No public exploit | Cloud Foundry UAA, all versions prior to 4.20.0 and Cloud Foundry UAA Release, all versions prior to 61.0, allows brute forcing of MFA codes. A remote unauthenticated malicious user in possession of a valid username and password can brute force MFA to login as the targeted user. |
| CVE-2018-1223 | High | 2018-09-17 | Not applicable | No public exploit | Cloud Foundry Container Runtime (kubo-release), versions prior to 0.14.0, may leak UAA and vCenter credentials to application logs. A malicious user with the ability to read the application logs could use these credentials to escalate privileges. |
| CVE-2016-0715 | Medium | 2018-09-11 | Not applicable | No public exploit | Pivotal Cloud Foundry Elastic Runtime version 1.4.0 through 1.4.5, 1.5.0 through 1.5.11 and 1.6.0 through 1.6.11 is vulnerable to a remote information disclosure. It was found that original mitigation configuration instructions provided as part of CVE-2016-0708 were incomplete and could leave PHP Buildpack, Staticfile Buildpack and potentially other custom Buildpack applications vulnerable to remote information disclosure. Affected applications use automated buildpack detection, serve files directly from the root of the application and have a buildpack that matched after the Java Buildpack in the system buildpack priority when Java Buildpack versions 2.0 through 3.4 were present. |