pysec-2019-147
Vulnerability from pysec
Published
2019-01-23 17:29
Modified
2021-07-05 00:01
Details

In Apache Airflow 1.8.2 and earlier, an authenticated user can execute code remotely on the Airflow webserver by creating a special object.

Impacted products
Name purl
apache-airflow pkg:pypi/apache-airflow



{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "apache-airflow",
            purl: "pkg:pypi/apache-airflow",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "1.9.0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "1.8.1",
            "1.8.2",
            "1.8.2rc1",
         ],
      },
   ],
   aliases: [
      "CVE-2017-15720",
      "GHSA-8fg4-j562-mjrc",
   ],
   details: "In Apache Airflow 1.8.2 and earlier, an authenticated user can execute code remotely on the Airflow webserver by creating a special object.",
   id: "PYSEC-2019-147",
   modified: "2021-07-05T00:01:17.000324Z",
   published: "2019-01-23T17:29:00Z",
   references: [
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/ade4d54ebf614f68dc81a08891755e60ea58ba88e0209233eeea5f57@%3Cdev.airflow.apache.org%3E",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-8fg4-j562-mjrc",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

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.
  • 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.