apache-airflow-providers-fab@3.1.1

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

  • latest version

    3.8.0

  • latest non vulnerable version

  • first published

    2 years ago

  • latest version published

    2 days ago

  • licenses detected

  • 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)
    • C
    LDAP Injection

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

    Affected versions of this package are vulnerable to LDAP Injection through the _ldap_bind_indirect and nested group search code in override.py. An attacker can manipulate the LDAP username or distinguished name used in the search filters by supplying crafted login input, causing the application to query unintended LDAP entries and authenticate or enumerate accounts incorrectly. This can let an attacker bypass intended LDAP lookup constraints and gain unauthorized access to the Airflow web application.

    Workarounds

    • Disable LDAP authentication in Airflow FAB Auth Manager until you can upgrade apache-airflow-providers-fab; this prevents unauthenticated attackers from abusing LDAP filter injection to exfiltrate directory data or bypass authentication.

    How to fix LDAP Injection?

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

    [,3.6.4rc1)
    • C
    Exposure of Resource to Wrong Sphere

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

    Affected versions of this package are vulnerable to Exposure of Resource to Wrong Sphere due to improper handling of the session token cookie path. An attacker can gain unauthorized access to user sessions by capturing valid session tokens through co-hosted applications operating under the same domain.

    How to fix Exposure of Resource to Wrong Sphere?

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

    [,3.5.0rc1)