CVE Vulnerability Catalog

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

This CVE ID has been rejected and contains no vulnerability information.

CVE-2021-47997 has been rejected. This means it is not a valid vulnerability and should not be considered in risk management processes.

Affected versions of Flowintel render calendar event titles using innerHTML. Because those titles are derived from case titles, a user able to create or modify a case title could store HTML or script-capable content that is later interpreted by the browser when another user views the calendar. The fix changes innerHTML to textContent.

Vulnerability in Flowintel allows JavaScript injection via malicious Mermaid blocks in case notes. An attacker with note creation or edit permissions can store a crafted payload that executes for other users.

Affected versions of Flowintel allow the LOG_FILE configuration value to be modified through system settings without restricting it to a filename inside the intended log directory. Because the application constructs the log destination from this configurable value, an administrator could set LOG_FILE to an arbitrary filesystem path. Since attackers can influence logged content, this enables controlled data to be written into unintended files. The upstream commit specifically describes an exploitation chain in which an attacker injects a template into a chosen file and subsequently abuses application rendering behavior to execute code. The patch removes LOG_FILE from the web-editable settings, introduces validate_log_file_name() to reject absolute paths, traversal, Windows paths, null bytes, and directory components, and centralizes log path construction through resolve_log_file_path(). Version impacted: >=3.3.0

The '/ws/apiprensa/getVideo' endpoint is vulnerable to SQL injection due to improper validation of the GET parameter `id_ambito`. An attacker can inject SQL syntax that breaks the underlying structure of the MariaDB query, resulting in syntax errors and the exposure of database error messages via PDOException. This confirms that user input is being incorporated directly into SQL statements without proper sanitization or the use of prepared statements.

A vulnerability in the endpoint '/ws/apitribuna/ultimosVideos' where the `limit_videos` parameter is directly concatenated into a MariaDB SQL query without proper sanitization or parameterization. By injecting SQL syntax into this parameter, a remote attacker can cause SQL syntax errors and potentially manipulate backend queries. The issue results in an error-based SQL injection and exposes internal database error messages and stack traces, revealing implementation details of the backend system.

The endpoint '/ws/apiprensa/getVideoUltimasSeccion' contains an SQL injection vulnerability in the id_seccion parameter. The parameter is directly embedded in a complex SQL query that includes grouping and sorting operations. By injecting SQL syntax, an attacker can disrupt the query structure and cause database errors, exposing the internal logic of the queries.

The endpoint '/ws/apiprensa/getVideoNextPrev' is vulnerable to SQL injection via the id_ambito parameter. Unsanitized input is directly incorporated into a MariaDB query, allowing attackers to inject SQL syntax that interrupts the query's execution. The vulnerability results in detailed database error messages and exposes the internal structure of the queries.

The '/ws/apitribuna/setVisita' endpoint is vulnerable to SQL injection through the id_video and id_ambito parameters. The application does not validate or sanitize these inputs before including them in SQL queries. This allows a remote attacker to inject SQL syntax and disrupt the execution of queries, causing database errors and potentially manipulating visit tracking records.

SQL injection vulnerability in the '/ws/apiprensa/getVideoSubcanal' endpoint due to improper handling of the id_video parameter. The application does not sanitize input before constructing SQL queries, which results in execution errors when malicious input is provided. The vulnerability exposes internal file paths and complete stack traces through the Slim framework's error handler, increasing severity.

Katello Content View Filter Rules API does not enforce authorization on the parent filter. A low-privileged user can access and modify filter rules in another organization.