feat: read security advisories from private GitHub repo (WT-1285) by stevejalim · Pull Request #17227 · mozilla/bedrock

stevejalim · 2026-06-12T11:06:32Z

One-line summary

This changeset switches Bedrock to read security advisories directly from the private GitHub repo, with PAT-based authentication plumbed through GitRepo.

Significant changes and points to review

Mozilla's security advisories are authored in a private GitHub repo that's been mirrored out to a public one (mozilla/foundation-security-advisories). Bedrock has read from the mirror. Keeping the two repos in sync has been a recurring operational pain point, so the mirror is being retired and Bedrock is moving to reading the private repo directly.

That means Bedrock needs authenticated GitHub access for this data flow for the first time.

Worth a careful review is how the token reaches the git subprocess: we use git's GIT_CONFIG_* env-var protocol to set http.extraheader for the duration of the subprocess. The token lives only in the subprocess environment; argv, the remote URL, the local .git/config, and the GitRepoState DB row all stay clean. When reviewing, pay particular attention to GitRepo._auth_env, GitRepo.clone and GitRepo.pull.

bedrock/settings/base.py flips the default MOFO_SECURITY_ADVISORIES_REPO to the private repo and adds the env-driven MOFO_SECURITY_ADVISORIES_AUTH setting. A small belt-and-braces tweak also adds "token", "auth", and "pat" to the Sentry sensitive-value blocklist alongside the existing with_default_keys defaults.

Deployment ordering note: MOFO_SECURITY_ADVISORIES_AUTH has been set in Dev, Stage, Test and Prod, but not in Demos. Existing SecurityAdvisory rows persist through any auth-failure window, so the demos will not start showing fresh advisories, but Dev and above will.

Issue / Bugzilla link

JIRA: https://mozilla-hub.atlassian.net/browse/WT-1285

Testing

I've tested this locally with the relevant auth token, so CI passing here and a human review is enough

stevejalim · 2026-06-12T11:08:04Z

FYI @simon-friedberger once this merges, it'll be rolled out with the next Bedrock release - usually the same day. Monday is a likely target, depending on when it gets reviewed

Copilot

Pull request overview

This PR updates Bedrock’s security advisories ingestion to pull directly from the private GitHub advisories repo, adding PAT-based authentication support to GitRepo and plumbing a new settings value through the update command.

Changes:

Add optional HTTP Basic auth for git clone/fetch via git’s GIT_CONFIG_* env-var protocol (token stays out of argv/URLs/config).
Switch MOFO_SECURITY_ADVISORIES_REPO default to the private repo and introduce MOFO_SECURITY_ADVISORIES_AUTH.
Expand git test coverage around auth parsing, env handling, and token non-leakage in argv.

Note: This review was performed following the repository’s custom Copilot instructions.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
`bedrock/utils/tests/test_git.py`	Adds tests for auth parsing/env creation and verifies tokens don’t land in argv/URLs.
`bedrock/utils/git.py`	Extends `GitRepo` to support authenticated clone/fetch via env-scoped git config and env merging.
`bedrock/settings/base.py`	Switches default advisories repo to private, adds `MOFO_SECURITY_ADVISORIES_AUTH`, and expands Sentry sensitive key list.
`bedrock/security/management/commands/update_security_advisories.py`	Passes the new auth setting into `GitRepo` for advisories updates.

codecov · 2026-06-12T11:35:37Z

Codecov Report

❌ Patch coverage is 97.82609% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 82.84%. Comparing base (31f3cb6) to head (59e9807).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
bedrock/utils/git.py	97.36%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17227      +/-   ##
==========================================
+ Coverage   82.72%   82.84%   +0.11%     
==========================================
  Files         178      178              
  Lines        9373     9413      +40     
==========================================
+ Hits         7754     7798      +44     
+ Misses       1619     1615       -4

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

janriokrause

PAT can still leak via Sentry locals. _auth_env() puts base64(username:token) in GIT_CONFIG_VALUE_0, and git() carries it through env/kwargs. On clone/fetch failure, Sentry may capture those locals. Current redaction names may not catch the encoded credential. What do you think?

Copilot

Pull request overview

Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.

janriokrause

r+ Thank you!

Mozilla's security advisories are authored in a private GitHub repo and then synced out to a public mirror. Bedrock has historically read from the mirror. Keeping the two repos in sync has been a recurring operational pain point, so we're retiring the mirror and having Bedrock read directly from the private repo. That means Bedrock now needs authenticated access to GitHub for this data flow for the first time. GitRepo gains an optional auth kwarg accepting a "<user>:<token>" string (matching the existing FLUENT_REPO_AUTH convention). When set, an internal context manager supplies HTTP Basic auth via git's GIT_CONFIG_COUNT / GIT_CONFIG_KEY_0 / GIT_CONFIG_VALUE_0 env-var protocol, which sets a host-scoped http.<scheme>://<host>/.extraheader for the duration of the subprocess. Scoping by host means the Authorization header won't follow incidental redirects or LFS fetches against unrelated hosts during the clone or fetch; falls back to the unscoped global key for non-HTTPS remotes. The token never enters argv, the remote URL, the local .git/config, or the GitRepoState DB row. That keeps it out of any CalledProcessError payload and out of the Sentry event produced by the @alert_sentry_on_exception decorator on the management command. This is why we chose extraheader over the simpler token-in-URL pattern used elsewhere in the codebase. bedrock/settings/base.py adds a new MOFO_SECURITY_ADVISORIES_AUTH setting (env-driven, empty by default), flips the default MOFO_SECURITY_ADVISORIES_REPO to the private repo URL, and gains "token", "auth", "pat", and "git_config_value" entries on the Sentry desensitization blocklist. The first three protect against future variable-name drift; "git_config_value" specifically catches GIT_CONFIG_VALUE_0 (and any future _1/_2/...) since those keys don't substring-match the default blocklist -- without it, an exception in GitRepo.git would let the base64-encoded credential survive into the Sentry payload via the captured env / kwargs locals. A targeted test in test_sentry.py exercises that path with a realistic AUTHORIZATION: Basic <base64> payload. .env-dist gains a commented entry documenting the new var. update_security_advisories passes the auth setting through to GitRepo and skips entirely if MOFO_SECURITY_ADVISORIES_AUTH is missing -- there is no useful sync work to do without a PAT against the private repo. Prints a short "Skipping..." line so bin/run-db-update.sh logs make the reason visible. bin/run-db-update.sh moves the update_security_advisories invocation inside the AUTH=true block so the docker image build (which has no secrets) doesn't even attempt to run it. Deployment note: MOFO_SECURITY_ADVISORIES_AUTH must be present in the deployment secret store. Without it, the cron run skips the security-advisories step (printed to stdout, no Sentry alert). Existing SecurityAdvisory rows persist through any outage, so the public-facing pages keep serving while the secret is being put in place.

Copilot

Pull request overview

Copilot reviewed 9 out of 10 changed files in this pull request and generated 3 comments.

stevejalim requested a review from a team as a code owner June 12, 2026 11:06

stevejalim requested review from Copilot and janriokrause June 12, 2026 11:07

Copilot started reviewing on behalf of stevejalim June 12, 2026 11:07 View session

stevejalim force-pushed the WT-1285--move-sec-advisories-source-to-private-repo branch from 64b3d88 to 4088a41 Compare June 12, 2026 11:08

stevejalim changed the title ~~feat(security): read advisories from private GitHub repo (WT-1285)~~ feat: read security advisories from private GitHub repo (WT-1285) Jun 12, 2026

Copilot AI reviewed Jun 12, 2026

View reviewed changes

Comment thread bedrock/utils/git.py

Comment thread bedrock/settings/base.py

stevejalim force-pushed the WT-1285--move-sec-advisories-source-to-private-repo branch from 4088a41 to aaf36d2 Compare June 12, 2026 11:26

janriokrause reviewed Jun 15, 2026

View reviewed changes

stevejalim requested review from Copilot and janriokrause June 17, 2026 10:20

Copilot started reviewing on behalf of stevejalim June 17, 2026 10:21 View session

Copilot AI reviewed Jun 17, 2026

View reviewed changes

Comment thread bedrock/security/management/commands/update_security_advisories.py Outdated

stevejalim force-pushed the WT-1285--move-sec-advisories-source-to-private-repo branch 2 times, most recently from 9e1114b to 7e98bb1 Compare June 17, 2026 12:48

janriokrause approved these changes Jun 17, 2026

View reviewed changes

stevejalim force-pushed the WT-1285--move-sec-advisories-source-to-private-repo branch from 7e98bb1 to f1a1fbc Compare June 22, 2026 09:09

stevejalim force-pushed the WT-1285--move-sec-advisories-source-to-private-repo branch from f1a1fbc to 59e9807 Compare June 22, 2026 10:26

stevejalim requested a review from a team as a code owner June 22, 2026 10:26

stevejalim requested a review from Copilot June 22, 2026 10:44

Copilot started reviewing on behalf of stevejalim June 22, 2026 10:44 View session

Copilot AI reviewed Jun 22, 2026

View reviewed changes

Comment thread bedrock/security/management/commands/update_security_advisories.py

Comment thread bedrock/base/templates/cron-health-check.html

Comment thread .env-dist

stevejalim merged commit 5c10851 into main Jun 22, 2026
7 checks passed

stevejalim deleted the WT-1285--move-sec-advisories-source-to-private-repo branch June 22, 2026 11:05

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: read security advisories from private GitHub repo (WT-1285)#17227

feat: read security advisories from private GitHub repo (WT-1285)#17227
stevejalim merged 1 commit into
mainfrom
WT-1285--move-sec-advisories-source-to-private-repo

stevejalim commented Jun 12, 2026

Uh oh!

stevejalim commented Jun 12, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

codecov Bot commented Jun 12, 2026 •

edited

Loading

Uh oh!

janriokrause left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

janriokrause left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

stevejalim commented Jun 12, 2026

One-line summary

Significant changes and points to review

Testing

Uh oh!

stevejalim commented Jun 12, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

codecov Bot commented Jun 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

janriokrause left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

janriokrause left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

codecov Bot commented Jun 12, 2026 •

edited

Loading