Vulnerabilidades

*** Pendiente de traducción *** An attacker can bypass authorization checks and force a Step CA ACME or SCEP provisioner to create certificates without completing certain protocol authorization checks.

*** Pendiente de traducción *** In python-jose 3.3.0 (specifically jwe.decrypt), a vulnerability allows an attacker to cause a Denial-of-Service (DoS) condition by crafting a malicious JSON Web Encryption (JWE) token with an exceptionally high compression ratio. When this token is processed by the server, it results in significant memory allocation and processing time during decompression.

*** Pendiente de traducción *** In jose4j before 0.9.5, an attacker can cause a Denial-of-Service (DoS) condition by crafting a malicious JSON Web Encryption (JWE) token with an exceptionally high compression ratio. When this token is processed by the server, it results in significant memory allocation and processing time during decompression.

*** Pendiente de traducción *** Netaxis API Orchestrator (APIO) before 0.19.3 allows server side template injection (SSTI).

*** Pendiente de traducción *** CSRF in Ercom Cryptobox administration console allows attacker to trigger some actions on behalf of a Cryptobox administrator. The attack requires the administrator to browse a malicious web site or to click a link while he has an open session on the administration console.

*** Pendiente de traducción *** Successful exploitation of this vulnerability could result in the product failing to re-establish communication once the certificate expires.

*** Pendiente de traducción *** Mattermost versions 11.0.x

*** Pendiente de traducción *** Mattermost versions 10.11.x

*** Pendiente de traducción *** A vulnerability in the application software of multiple Radiometer products may allow remote code execution and unauthorized device management when specific internal conditions are met. Exploitation requires that a remote connection is established with additional information obtained through other means. The issue is caused by a weakness in the analyzer’s application software.                                                                                                                                                                                                Other related CVE&amp;#39;s are CVE-2025-14095 &amp; CVE-2025-14096.                                                                                                      Affected customers have been informed about this vulnerability. This CVE is being published to provide transparency.<br /> <br /> <br /> <br /> Required Configuration for Exposure: Affected application software version is in use and remote support feature is enabled in the analyzer.                                                                                                                                                                        Temporary work Around: If the network is not considered secure, please remove the analyzer from the network.                         Permanent solution:<br /> Customers should ensure the following:<br /> • The network is secure, and access follows best practices.<br /> Local Radiometer representatives will contact all affected customers to discuss a permanent solution.                                                     <br /> Exploit Status:<br /> <br /> <br /> Researchers have provided working proof-of-concept (PoC). Radiometer is not aware of any publicly available exploits at the time of this publication.

*** Pendiente de traducción *** A vulnerability exists in multiple Radiometer products that allow an attacker with physical access to the analyzer possibility to extract credential information. The vulnerability is due to a weakness in the design and insufficient credential protection in operating system.<br /> <br /> Other related CVE&amp;#39;s are CVE-2025-14095 &amp; CVE-2025-14097.<br /> <br /> <br /> <br /> Affected customers have been informed about this vulnerability. This CVE is being published to provide transparency.<br /> <br /> <br /> <br /> <br /> <br /> Required Configuration for Exposure:<br /> <br /> <br /> Attacker requires physical access to the analyzer.<br /> <br /> <br /> <br /> Temporary work Around:<br /> Only authorized people can physically access the analyzer.<br /> <br /> Permanent solution:<br /> Local Radiometer representatives will contact all affected customers to discuss a permanent solution.<br /> <br /> Exploit Status:<br /> <br /> <br /> Researchers have provided a working proof-of-concept (PoC). Radiometer is not aware of any public exploit code at the time of this publication.

*** Pendiente de traducción *** Mattermost versions 10.11.x

*** Pendiente de traducción *** Edge3 Worker RPC RCE on Airflow 2.<br /> <br /> This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if you installed and configured it on Airflow 2.<br /> <br /> <br /> <br /> The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if you installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do.<br /> <br /> If you installed and configured Edge3 provider for Airflow 2, you should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (&gt;=2.0.0) has minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2.<br /> <br /> If you used Edge Provider in Airflow 3, you are not affected.