Hydra logging configuration permits unsafe callable resolution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| hydra-ecosystem | hydra | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hydra-ecosystem | Hydra |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-c3wx-c55w-pxjq | Hydra logging configuration permits unsafe callable resolution |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.165% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hydra-ecosystem
Hydra-ecosystem hydra |
|
| Vendors & Products |
Hydra-ecosystem
Hydra-ecosystem hydra |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-470 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Hydra is a framework for elegantly configuring complex applications. Prior to 1.3.6 and 1.4.0.dev9, Hydra passes Python logging configuration to logging.config.dictConfig() without applying Hydra's target policy to handler class values or formatter, filter, handler, queue, and listener factories. An attacker who controls Hydra logging configuration can therefore select an importable class or factory and cause it to be invoked with the application's privileges, even in versions where instantiate() is protected because the logging path does not use instantiate(). This issue is fixed in versions 1.3.6 and 1.4.0.dev9. | |
| Title | Hydra logging configuration permits unsafe callable resolution | |
| Weaknesses | CWE-94 | |
| References |
|
|
| Metrics |
cvssV3_1
|