pysec-2024-13
Vulnerability from pysec
Published
2024-01-24 13:15
Modified
2024-01-24 16:22
Details
Apache Airflow, versions before 2.8.1, have a vulnerability that allows a potential attacker to poison the XCom data by bypassing the protection of "enable_xcom_pickling=False" configuration setting resulting in poisoned data after XCom deserialization. This vulnerability is considered low since it requires a DAG author to exploit it. Users are recommended to upgrade to version 2.8.1 or later, which fixes this issue.
Impacted products
| Name | purl | apache-airflow | pkg:pypi/apache-airflow |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "apache-airflow",
"purl": "pkg:pypi/apache-airflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.8.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.10.0",
"1.10.1",
"1.10.10",
"1.10.10rc1",
"1.10.10rc2",
"1.10.10rc3",
"1.10.10rc4",
"1.10.10rc5",
"1.10.11",
"1.10.11rc1",
"1.10.11rc2",
"1.10.12",
"1.10.12rc1",
"1.10.12rc2",
"1.10.12rc3",
"1.10.12rc4",
"1.10.13",
"1.10.13rc1",
"1.10.14",
"1.10.14rc1",
"1.10.14rc2",
"1.10.14rc3",
"1.10.14rc4",
"1.10.15",
"1.10.15rc1",
"1.10.1b1",
"1.10.1rc2",
"1.10.2",
"1.10.2b2",
"1.10.2rc1",
"1.10.2rc2",
"1.10.2rc3",
"1.10.3",
"1.10.3b1",
"1.10.3b2",
"1.10.3rc1",
"1.10.3rc2",
"1.10.4",
"1.10.4b2",
"1.10.4rc1",
"1.10.4rc2",
"1.10.4rc3",
"1.10.4rc4",
"1.10.4rc5",
"1.10.5",
"1.10.5rc1",
"1.10.6",
"1.10.6rc1",
"1.10.6rc2",
"1.10.7",
"1.10.7rc1",
"1.10.7rc2",
"1.10.7rc3",
"1.10.8",
"1.10.8rc1",
"1.10.9",
"1.10.9rc1",
"1.8.1",
"1.8.2",
"1.8.2rc1",
"1.9.0",
"2.0.0",
"2.0.0b1",
"2.0.0b2",
"2.0.0b3",
"2.0.0rc1",
"2.0.0rc2",
"2.0.0rc3",
"2.0.1",
"2.0.1rc1",
"2.0.1rc2",
"2.0.2",
"2.0.2rc1",
"2.1.0",
"2.1.0rc1",
"2.1.0rc2",
"2.1.1",
"2.1.1rc1",
"2.1.2",
"2.1.2rc1",
"2.1.3",
"2.1.3rc1",
"2.1.4",
"2.1.4rc1",
"2.1.4rc2",
"2.2.0",
"2.2.0b1",
"2.2.0b2",
"2.2.0rc1",
"2.2.1",
"2.2.1rc1",
"2.2.1rc2",
"2.2.2",
"2.2.2rc1",
"2.2.2rc2",
"2.2.3",
"2.2.3rc1",
"2.2.3rc2",
"2.2.4",
"2.2.4rc1",
"2.2.5",
"2.2.5rc1",
"2.2.5rc2",
"2.2.5rc3",
"2.3.0",
"2.3.0b1",
"2.3.0rc1",
"2.3.0rc2",
"2.3.1",
"2.3.1rc1",
"2.3.2",
"2.3.2rc1",
"2.3.2rc2",
"2.3.3",
"2.3.3rc1",
"2.3.3rc2",
"2.3.3rc3",
"2.3.4",
"2.3.4rc1",
"2.4.0",
"2.4.0b1",
"2.4.0rc1",
"2.4.1",
"2.4.1rc1",
"2.4.2",
"2.4.2rc1",
"2.4.3",
"2.4.3rc1",
"2.5.0",
"2.5.0rc1",
"2.5.0rc2",
"2.5.0rc3",
"2.5.1",
"2.5.1rc1",
"2.5.1rc2",
"2.5.2",
"2.5.2rc1",
"2.5.2rc2",
"2.5.3",
"2.5.3rc1",
"2.5.3rc2",
"2.6.0",
"2.6.0b1",
"2.6.0rc1",
"2.6.0rc2",
"2.6.0rc3",
"2.6.0rc4",
"2.6.0rc5",
"2.6.1",
"2.6.1rc1",
"2.6.1rc2",
"2.6.1rc3",
"2.6.2",
"2.6.2rc1",
"2.6.2rc2",
"2.6.3",
"2.6.3rc1",
"2.7.0",
"2.7.0b1",
"2.7.0rc1",
"2.7.0rc2",
"2.7.1",
"2.7.1rc1",
"2.7.1rc2",
"2.7.2",
"2.7.2rc1",
"2.7.3",
"2.7.3rc1",
"2.8.0",
"2.8.0b1",
"2.8.0rc1",
"2.8.0rc2",
"2.8.0rc3",
"2.8.0rc4",
"2.8.1rc1"
]
}
],
"aliases": [
"CVE-2023-50943"
],
"details": "Apache Airflow, versions before 2.8.1, have a vulnerability that allows a potential attacker to poison the XCom data by bypassing the protection of \"enable_xcom_pickling=False\" configuration setting resulting in poisoned data after XCom deserialization. This vulnerability is considered low since it requires a DAG author to exploit it. Users are recommended to upgrade to version 2.8.1 or later, which fixes this issue.\n",
"id": "PYSEC-2024-13",
"modified": "2024-01-24T16:22:57.352530+00:00",
"published": "2024-01-24T13:15:00+00:00",
"references": [
{
"type": "WEB",
"url": "https://github.com/apache/airflow/pull/36255"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread/fx278v0twqzxkcts70tc04cp3f8p56pn"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…