CVE Vulnerability Catalog

A user with query access to an Azure Monitor data source can use its resource proxy to call Azure Resource Manager APIs beyond those Grafana needs, with the data source's Azure identity (unintended proxy). The impact is bounded by the Azure role granted to that identity.

Potential arbitrary code execution under specific configurations. An updated note states that affected versions now include JFrog CLI v2.127.0.

DeepSeek V4 is vulnerable to Incorrect Access Control via a crafted input.

An issue in HTMLy v.3.1.1 allows a remote attacker to escalate privileges via the get_feed function in the admin.php component.

The Prometheus rule conversion API endpoints in Grafana do not limit request body size, allowing authenticated users to trigger unbounded memory allocations that can crash the server through out-of-memory conditions.

An SQL Injection vulnerability (CWE-89) in Fortinet FortiAnalyzer and FortiManager (including Cloud versions) allows a low-privileged user to execute arbitrary commands via crafted requests. It affects multiple versions of Fortinet software.

Fortinet FortiAnalyzer 7.6.0 through 7.6.2, 7.4.1 through 7.4.6, FortiAnalyzer Cloud 7.6.2, 7.4.1 through 7.4.6, 7.2.1 through 7.2.9, and FortiManager 7.6.0 through 7.6.2, 7.4.0 through 7.4.6 contain an SQL Injection vulnerability (CWE-89). It may allow a low-privileged user to execute arbitrary commands via crafted requests.

An SQL Injection vulnerability (CWE-89) in Fortinet FortiAnalyzer and FortiManager may allow a low-privileged user to execute arbitrary commands via crafted requests. This affects FortiAnalyzer 7.6.0 through 7.6.2, 7.4.0 through 7.4.6, 7.2.0 through 7.2.12, and FortiManager 7.4.0 through 7.4.6 and 7.2 all versions.

A user or service account with read-only access to Git Sync (provisioning) connections can modify a connection's configuration through its status subresource (incorrect authorization). On Grafana 12.4 the affected API is only available when the experimental provisioning feature toggle is enabled.

The dataclasses-avroschema library versions 0.38.0 through 0.70.5 does not validate enum symbols as identifiers, allowing injection of statements into the generated enum class. This can lead to namespace modification or prevent the module from loading.

The dataclasses-avroschema library versions 0.38.0 through 0.70.5 improperly handles the aliases value of a fixed type, inserting it unquoted into a types.confixed annotation. This allows arbitrary Python code execution when the generated module is imported.

The dataclasses-avroschema library versions 0.38.0 through 0.70.5 does not validate the default value of an enum field as an identifier, allowing injection of statements into the generated module. This can lead to namespace modification or prevent the module from loading.

The dataclasses-avroschema library versions 0.38.0 through 0.70.5 does not escape enum symbols, allowing injection of arbitrary Python code into the enum class body. This code executes when the generated module is imported.

The dataclasses-avroschema library versions 0.44.0 through 0.70.5 does not safely restrict the pydantic-class value in field annotations, allowing arbitrary Python code execution when the generated module is imported. It affects Pydantic and AvroDantic model generators.

The dataclasses-avroschema library versions 0.65.9 through 0.70.5 does not escape the doc value inserted into the description argument of pydantic.Field, allowing injection of an expression and arbitrary Python code execution during class definition. It affects Pydantic and AvroDantic model generation.

The dataclasses-avroschema library versions 0.38.0 through 0.70.5 does not escape or validate the namespace value of a fixed type, inserting it in quotes into a types.confixed annotation. This allows arbitrary Python code execution when the generated class is defined.

dataclasses-avroschema versions 0.40.0 through 0.70.5 fail to escape quotes or backslashes when copying a schema record's doc value into a generated class docstring. A crafted triple-quote sequence can close the docstring and inject statements into the generated class body, leading to Python code execution during module import.

dataclasses-avroschema versions 0.62.3 through 0.70.5 insert a schema-controlled Avro record name into the quoted Meta.schema_name field of generated Python source without escaping it. A crafted name can terminate the string literal and inject statements into the generated class body that execute when the module is imported.

dataclasses-avroschema versions 0.47.3 through 0.70.5 insert a schema-controlled referenced record name into the callable position of a generated default_factory lambda without validating it as an Avro name. A crafted record name can become an arbitrary Python expression that executes when an instance of the generated model consumes the field default.

dataclasses-avroschema versions 0.38.0 through 0.70.5 insert schema-controlled string, UUID, bytes, and fixed field defaults into quoted literals in generated Python source without escaping them. A crafted default can terminate the literal and inject statements into the generated module that execute when the module is imported.