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-2018-2483

Publication date:

13/11/2018

HTTP Verb Tampering is possible in SAP BusinessObjects Business Intelligence Platform, versions 4.1 and 4.2, Central Management Console (CMC) by changing request method.

Severity CVSS v4.0: Pending analysis

Last modification:

24/08/2020

CVE-2018-2487

Publication date:

13/11/2018

SAP Disclosure Management 10.x allows an attacker to exploit through a specially crafted zip file provided by users: When extracted in specific use cases, files within this zip file can land in different locations than the originally intended extraction point.

Severity CVSS v4.0: Pending analysis

Last modification:

24/08/2020

CVE-2018-2488

Publication date:

13/11/2018

It is possible for a malware application installed on an Android device to send local push notifications with an empty message to SAP Fiori Client and cause the application to crash. SAP Fiori Client version 1.11.5 in Google Play store addresses these issues and users must update to that version.

Severity CVSS v4.0: Pending analysis

Last modification:

24/08/2020

CVE-2018-7910

Publication date:

13/11/2018

Some Huawei smartphones ALP-AL00B 8.0.0.118D(C00), ALP-TL00B 8.0.0.118D(C01), BLA-AL00B 8.0.0.118D(C00), BLA-L09C 8.0.0.127(C432), 8.0.0.128(C432), 8.0.0.137(C432), BLA-L29C 8.0.0.129(C432), 8.0.0.137(C432) have an authentication bypass vulnerability. When the attacker obtains the user&#39;s smartphone, the vulnerability can be used to replace the start-up program so that the attacker can obtain the information in the smartphone and achieve the purpose of controlling the smartphone.

Severity CVSS v4.0: Pending analysis

Last modification:

12/12/2018

CVE-2018-7925

Publication date:

13/11/2018

The radio module of some Huawei smartphones Emily-AL00A The versions before 8.1.0.171(C00) have a lock-screen bypass vulnerability. An unauthenticated attacker could start third-part input method APP through certain operations to bypass lock-screen by exploit this vulnerability.

Severity CVSS v4.0: Pending analysis

Last modification:

03/10/2019

CVE-2018-7926

Publication date:

13/11/2018

Huawei Watch 2 with versions and earlier than OWDD.180707.001.E1 have an improper authorization vulnerability. Due to improper permission configuration for specific operations, an attacker who obtained the Huawei ID bound to the watch can bypass permission verification to perform specific operations and modify some data on the watch.

Severity CVSS v4.0: Pending analysis

Last modification:

03/10/2019

CVE-2018-12416

Publication date:

13/11/2018

The GridServer Broker and GridServer Director components of TIBCO Software Inc.&#39;s TIBCO DataSynapse GridServer Manager contain vulnerabilities which may allow an unauthenticated user to perform cross-site request forgery (CSRF). Affected releases are TIBCO Software Inc. TIBCO DataSynapse GridServer Manager: versions up to and including 5.2.0; 6.0.0; 6.0.1; 6.0.2; 6.1.0; 6.1.1; 6.2.0; 6.3.0.

Severity CVSS v4.0: Pending analysis

Last modification:

09/10/2019

CVE-2018-14655

Publication date:

13/11/2018

A flaw was found in Keycloak 3.4.3.Final, 4.0.0.Beta2, 4.3.0.Final. When using &#39;response_mode=form_post&#39; it is possible to inject arbitrary Javascript-Code via the &#39;state&#39;-parameter in the authentication URL. This allows an XSS-Attack upon succesfully login.

Severity CVSS v4.0: Pending analysis

Last modification:

09/10/2019

CVE-2018-14658

Publication date:

13/11/2018

A flaw was found in JBOSS Keycloak 3.2.1.Final. The Redirect URL for both Login and Logout are not normalized in org.keycloak.protocol.oidc.utils.RedirectUtils before the redirect url is verified. This can lead to an Open Redirection attack

Severity CVSS v4.0: Pending analysis

Last modification:

09/10/2019

CVE-2018-14657

Publication date:

13/11/2018

A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final. When TOPT enabled, an improper implementation of the Brute Force detection algorithm will not enforce its protection measures.

Severity CVSS v4.0: Pending analysis

Last modification:

02/02/2023

CVE-2018-6260

Publication date:

13/11/2018

NVIDIA graphics driver contains a vulnerability that may allow access to application data processed on the GPU through a side channel exposed by the GPU performance counters. Local user access is required. This is not a network or remote attack vector.

Severity CVSS v4.0: Pending analysis

Last modification:

18/04/2019

CVE-2018-17187

Publication date:

13/11/2018

The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the &#39;transport.ssl(...)&#39; methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.

Severity CVSS v4.0: Pending analysis

Last modification:

31/01/2019

Subscribe to Vulnerabilities