Homepage

apache-airflow-providers-fab@3.7.0rc1

Provider package apache-airflow-providers-fab for Apache Airflow

  • latest version

    3.7.3

  • latest non vulnerable version

    3.8.0rc2

  • first published

    2 years ago

  • latest version published

    10 days ago

  • licenses detected

  • View apache-airflow-providers-fab package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the apache-airflow-providers-fab package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Improper Verification of Cryptographic Signature

    apache-airflow-providers-fab is a Provider package apache-airflow-providers-fab for Apache Airflow

    Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to the verify_signature parameter in the Azure AD OAuth login defaulting to False, which disables JWT signature verification. An attacker can gain unauthorized access as any user, including those with administrative privileges, by presenting a forged or unsigned ID token to the OAuth callback.

    Note: This is only exploitable if the FAB auth manager is configured with the Azure AD OAuth login path using its default settings.

    How to fix Improper Verification of Cryptographic Signature?

    Upgrade apache-airflow-providers-fab to version 3.7.3 or higher.

    [,3.7.3)
    • H
    Use of Incorrectly-Resolved Name or Reference

    apache-airflow-providers-fab is a Provider package apache-airflow-providers-fab for Apache Airflow

    Affected versions of this package are vulnerable to Use of Incorrectly-Resolved Name or Reference through the resource_name() function in permissions.py and the mirrored core permissions module. An attacker can gain global read/edit access to all DAGs by creating or targeting a DAG with the dag_id DAGs and having per-DAG access_control granted on that DAG. The vulnerable resource_name() logic returned the raw dag_id when it matched a reserved resource name, so the valid DAG name DAGs collided with the global all-DAGs permission resource instead of resolving to its own DAG:DAGs resource. As a result, permissions intended for one DAG were applied to the global DAGs resource, exposing every DAG to the lower-privileged user.

    Notes

    • The issue affects both the FAB auth-manager permissions helper and the mirrored core permissions helper, so deployments using either copy of Airflow’s permission resolution can inherit the same resource-name collision.

    How to fix Use of Incorrectly-Resolved Name or Reference?

    Upgrade apache-airflow-providers-fab to version 3.7.2rc1 or higher.

    [,3.7.2rc1)
    Go back to all versions of this package