Impact What kind of vulnerability is it? Who is impacted?

When a user installs a package in dbt, it has the ability to override macros, materializations, and other core components of dbt. This is by design, as it allows packages to extend and customize dbt's functionality. However, this also means that a malicious package could potentially override these components with harmful code.

Patches Has the problem been patched? What versions should users upgrade to?

Fixed on 1.8.0, and patched for 1.6.14 and 1.7.14 releases.

Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading?

Previously, a materialization defined in a package that shared a name with one of the built-in materializations would be preferred by default, without user action which is surprising and makes it more difficult to detect the insecure behaviour. We've changed the default behaviour to require explicit overrides by users in 1.8.0, and provided the ability to opt-out of built-in materialization overrides in 1.6 and 1.7 via the flags.requireexplicitpackageoverridesforbuiltinmaterializations: False configuration in dbtproject.yml

Versions older than 1.6 are EOL.

References Are there any links users can visit to find out more? dbt documentation: https://docs.getdbt.com/reference/global-configs/legacy-behaviors#behavior-change-flags https://www.elementary-data.com/post/are-dbt-packages-secure-the-answer-lies-in-your-dwh-policies https://www.equalexperts.com/blog/tech-focus/are-you-at-risk-from-this-critical-dbt-vulnerability/ https://tempered.works/posts/2024/07/06/preventing-data-theft-with-gcp-service-controls/

End of life: 12/3/2022, End of support: 4/28/2022, Latest version: 1.0.9

End of life: 12/3/2022, End of support: 4/28/2022, Latest version: 1.0.9