The `access_key` and `connection_string` connection properties were not marked as sensitive names in secrets masker. This means that user with read permission could see the values in Connection UI, as well as when Connection was accidentaly logged to logs, those values could be seen in the logs. Azure Service Bus used those properties to store sensitive values. Possibly other providers could be also affected if they used the same fields to store sensitive data. If you used Azure Service Bus connection with those values set or if you have other connections with those values storing sensitve values, you should upgrade Airflow to 3.1.8
| Vendor | Product | Versions |
|---|---|---|
| apache | airflow | pip/apache-airflow: < 3.1.8 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| apache | airflow | cert_advisory | 90% |
Updated severity to LOW, marked exploit as available, and indicated active exploitation.
Updated affected versions to include 3.1.7, changed severity to HIGH, and noted that no exploit is available.
Initial creation
