Skip to content

dbt-core vulnerability PVE-2024-73530

SafetyCLI check output for the vulnerability

I noticed failing builds this week, with a dbt-core vulnerability flagged by SafetyCLI as the culprit. There was no actionable information in the command line output, so here's what I found and my action.

  • Thanks to Equal Experts logo for supporting this content.

About PVE-2024-73530

PVE-2024-73530 is, I believe, an identifier assigned by SafetyCLI themselves. Information is limited without a SafetyCLI account. I tried to sign up for an account this morning, but I'm getting errors back, so I can't actually see the specific issues and remediations. I raised the issue to SafetyCLI.

What we can see says it's related to "improper access control", CWE-284. A link from the linked page points to this commit from May 2024, which addressed a risk related to how the local web server associated with dbt docs serve was configured. I can't see anything wrong in there. I can also see that the issue was created on October 1st, just over a month ago - so if there is a significant risk, we've already been exposed to it for a month.

Looking at Snyk, I can't find any indication of an issue there. If I were just using Snyk, I don't think I'd have any indication of a security problem at this point.

Finally, I looked on the dbt-core repo for any indications of what the issue might be and came up empty. The issue is in the public domain as it's flagged by SafetyCLI, but I've raised a private security disclosure with dbt Labs to ensure awareness and get any advice they might have.

So... not a lot to go on, and not the best position to be in, given that I have to make decisions about what to do.

Actions

Given the lack of information, I do feel a bit exposed. Hopefully, SafetyCLI or dbt Labs will be able to share more information with me soon, and I'll update the post accordingly.

For now, it seems the only choices are to either not use dbt or "ignore" the vulnerability until more information is available.

If I choose to ignore it, I can add that to the .safety-policy.yml files to expire tomorrow, which will allow work to continue but force a review when I try to use dbt after that point, whether that's locally, in Codespaces or CI/CD automation.

It's easy to say "vulnerability management process" but the day-to-day reality is tricky...

Feedback

If you want to get in touch with me about the content in this post, you can find me on LinkedIn or raise an issue/start a discussion in the GitHub repo. I'll be happy to credit you for any corrections or additions!

If you liked this, you can find content from other great consultants on the Equal Experts network blogs page 🎉