Vulnerabilities

With the aim of informing, warning and helping professionals with the latest security vulnerabilities in technology systems, we have made a database available for users interested in this information, which is in Spanish and includes all of the latest documented and recognised vulnerabilities.

This repository, with over 75,000 registers, is based on the information from the NVD (National Vulnerability Database) – by virtue of a partnership agreement – through which INCIBE translates the included information into Spanish.

On occasions this list will show vulnerabilities that have still not been translated, as they are added while the INCIBE team is still carrying out the translation process. The CVE  (Common Vulnerabilities and Exposures) Standard for Information Security Vulnerability Names is used with the aim to support the exchange of information between different tools and databases.

All vulnerabilities collected are linked to different information sources, as well as available patches or solutions provided by manufacturers and developers. It is possible to carry out advanced searches, as there is the option to select different criteria to narrow down the results, some examples being vulnerability types, manufacturers and impact levels, among others.

Through RSS feeds or Newsletters we can be informed daily about the latest vulnerabilities added to the repository. Below there is a list, updated daily, where you can discover the latest vulnerabilities.

CVE-2021-42091

Publication date:
07/10/2021
An issue was discovered in Zammad before 4.1.1. SSRF can occur via GitHub or GitLab integration.
Severity CVSS v4.0: Pending analysis
Last modification:
14/10/2021

CVE-2021-42084

Publication date:
07/10/2021
An issue was discovered in Zammad before 4.1.1. An attacker with valid agent credentials may send a series of crafted requests that cause an endless loop and thus cause denial of service.
Severity CVSS v4.0: Pending analysis
Last modification:
14/10/2021

CVE-2020-21865

Publication date:
07/10/2021
ThinkPHP50-CMS v1.0 contains a remote code execution (RCE) vulnerability in the component /public/?s=captcha.
Severity CVSS v4.0: Pending analysis
Last modification:
14/10/2021

CVE-2021-42095

Publication date:
07/10/2021
Xshell before 7.0.0.76 allows attackers to cause a crash by triggering rapid changes to the title bar.
Severity CVSS v4.0: Pending analysis
Last modification:
15/10/2021

CVE-2021-42087

Publication date:
07/10/2021
An issue was discovered in Zammad before 4.1.1. An admin can discover the application secret via the API.
Severity CVSS v4.0: Pending analysis
Last modification:
12/07/2022

CVE-2021-42086

Publication date:
07/10/2021
An issue was discovered in Zammad before 4.1.1. An Agent account can modify account data, and gain admin access, via a crafted request.
Severity CVSS v4.0: Pending analysis
Last modification:
12/07/2022

CVE-2021-42092

Publication date:
07/10/2021
An issue was discovered in Zammad before 4.1.1. Stored XSS may occur via an Article during addition of an attachment to a Ticket.
Severity CVSS v4.0: Pending analysis
Last modification:
14/10/2021

CVE-2021-42093

Publication date:
07/10/2021
An issue was discovered in Zammad before 4.1.1. An admin can execute code on the server via a crafted request that manipulates triggers.
Severity CVSS v4.0: Pending analysis
Last modification:
14/10/2021

CVE-2021-42094

Publication date:
07/10/2021
An issue was discovered in Zammad before 4.1.1. Command Injection can occur via custom Packages.
Severity CVSS v4.0: Pending analysis
Last modification:
14/10/2021

CVE-2021-41130

Publication date:
07/10/2021
Extensible Service Proxy, a.k.a. ESP is a proxy which enables API management capabilities for JSON/REST or gRPC API services. ESPv1 can be configured to authenticate a JWT token. Its verified JWT claim is passed to the application by HTTP header "X-Endpoint-API-UserInfo", the application can use it to do authorization. But if there are two "X-Endpoint-API-UserInfo" headers from the client, ESPv1 only replaces the first one, the 2nd one will be passed to the application. An attacker can send two "X-Endpoint-API-UserInfo" headers, the second one with a fake JWT claim. Application may use the fake JWT claim to do the authorization. This impacts following ESPv1 usages: 1) Users have configured ESPv1 to do JWT authentication with Google ID Token as described in the referenced google endpoint document. 2) Users backend application is using the info in the "X-Endpoint-API-UserInfo" header to do the authorization. It has been fixed by v1.58.0. You need to patch it in the following ways: * If your docker image is using tag ":1", needs to re-start the container to pick up the new version. The tag ":1" will automatically point to the latest version. * If your docker image tag pings to a specific minor version, e.g. ":1.57". You need to update it to ":1.58" and re-start the container. There are no workaround for this issue.
Severity CVSS v4.0: Pending analysis
Last modification:
18/10/2021

CVE-2021-20571

Publication date:
07/10/2021
IBM Sterling B2B Integrator 5.2.0.0 through 6.1.1.0 is vulnerable to stored cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 199246.
Severity CVSS v4.0: Pending analysis
Last modification:
15/10/2021

CVE-2021-20561

Publication date:
07/10/2021
IBM Sterling File Gateway 2.2.0.0 through 6.1.1.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 199230.
Severity CVSS v4.0: Pending analysis
Last modification:
15/10/2021