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-2022-0203

Publication date:

26/01/2022

Improper Access Control in GitHub repository crater-invoice/crater prior to 6.0.2.

Severity CVSS v4.0: Pending analysis

Last modification:

02/02/2022

CVE-2022-0361

Publication date:

26/01/2022

Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.

Severity CVSS v4.0: Pending analysis

Last modification:

03/11/2025

CVE-2022-0359

Publication date:

26/01/2022

Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.

Severity CVSS v4.0: Pending analysis

Last modification:

03/11/2025

CVE-2021-44122

Publication date:

26/01/2022

SPIP 4.0.0 is affected by a Cross Site Request Forgery (CSRF) vulnerability in ecrire/public/aiguiller.php, ecrire/public/balises.php, ecrire/balise/formulaire_.php. To exploit the vulnerability, a visitor must visit a malicious website which redirects to the SPIP website. It is also possible to combine XSS vulnerabilities in SPIP 4.0.0 to exploit it. The vulnerability allows an authenticated attacker to execute malicious code without the knowledge of the user on the website (CSRF).

Severity CVSS v4.0: Pending analysis

Last modification:

02/02/2022

CVE-2021-44123

Publication date:

26/01/2022

SPIP 4.0.0 is affected by a remote command execution vulnerability. To exploit the vulnerability, an attacker must craft a malicious picture with a double extension, upload it and then click on it to execute it.

Severity CVSS v4.0: Pending analysis

Last modification:

02/02/2022

CVE-2021-44120

Publication date:

26/01/2022

SPIP 4.0.0 is affected by a Cross Site Scripting (XSS) vulnerability in ecrire/public/interfaces.php, adding the function safehtml to the vulnerable fields. An editor is able to modify his personal information. If the editor has an article written and available, when a user goes to the public site and wants to read the author&#39;s information, the malicious code will be executed. The "Who are you" and "Website Name" fields are vulnerable.

Severity CVSS v4.0: Pending analysis

Last modification:

01/02/2022

CVE-2021-44118

Publication date:

26/01/2022

SPIP 4.0.0 is affected by a Cross Site Scripting (XSS) vulnerability. To exploit the vulnerability, a visitor must browse to a malicious SVG file. The vulnerability allows an authenticated attacker to inject malicious code running on the client side into web pages visited by other users (stored XSS).

Severity CVSS v4.0: Pending analysis

Last modification:

01/02/2022

CVE-2022-22932

Publication date:

26/01/2022

Apache Karaf obr:* commands and run goal on the karaf-maven-plugin have partial path traversal which allows to break out of expected folder. The risk is low as obr:* commands are not very used and the entry is set by user. This has been fixed in revision: https://gitbox.apache.org/repos/asf?p=karaf.git;h=36a2bc4 https://gitbox.apache.org/repos/asf?p=karaf.git;h=52b70cf Mitigation: Apache Karaf users should upgrade to 4.2.15 or 4.3.6 or later as soon as possible, or use correct path. JIRA Tickets: https://issues.apache.org/jira/browse/KARAF-7326

Severity CVSS v4.0: Pending analysis

Last modification:

03/02/2022

CVE-2021-41766

Publication date:

26/01/2022

Apache Karaf allows monitoring of applications and the Java runtime by using the Java Management Extensions (JMX). JMX is a Java RMI based technology that relies on Java serialized objects for client server communication. Whereas the default JMX implementation is hardened against unauthenticated deserialization attacks, the implementation used by Apache Karaf is not protected against this kind of attack. The impact of Java deserialization vulnerabilities strongly depends on the classes that are available within the targets class path. Generally speaking, deserialization of untrusted data does always represent a high security risk and should be prevented. The risk is low as, by default, Karaf uses a limited set of classes in the JMX server class path. It depends of system scoped classes (e.g. jar in the lib folder).

Severity CVSS v4.0: Pending analysis

Last modification:

03/02/2022