Vendored pip trusts the compromised eMudhra root again
Categories
(Firefox Build System :: General, defect)
Tracking
(firefox-esr153 unaffected, firefox160 unaffected, firefox161 affected, firefox162 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr153 | --- | unaffected |
| firefox160 | --- | unaffected |
| firefox161 | --- | affected |
| firefox162 | --- | fixed |
People
(Reporter: drubino, Assigned: glandium, NeedInfo)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 external file)
Bug 2084865 updated pip's vendored certifi to 2026.10.19 to drop the eMudhra roots. The bug 2085860 re-vendor five days later put third_party/python/pip/pip/_vendor/certifi back to 2025.07.14, presumably because mach vendor python regenerates that folder from the pip 25.2 wheel.
On current main, cacert.pem in that folder contains emSign ECC Root CA - G3 again. A TLS connection that uses it as the CA file to https://dv-g3b-emudhra.we-have-a-problem.com/ (the public test host for one of the compromised intermediates) succeeds, where a fixed bundle rejects it.
Reapplying the certifi update by hand would presumably get undone by the next re-vendor... bumping vendored pip itself looks like the durable fix. pip 26.2.2 ships certifi 2026.10.19.
Follow-up to bug 2084865. Claude found this while checking my machine against the eMudhra advisory, and drafted this report.
Comment 1•7 days ago
|
||
Set release status flags based on info from the regressing bug 2085860
:ahochheiden, since you are the author of the regressor, bug 2085860, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 2•7 days ago
|
||
Bug 2085860 ran mach vendor python, which undid the changes from bug
2084865. Ensure future mach vendor python won't do the same by copying
the certifi files from the separately vendored version.
Updated•7 days ago
|
Comment 5•6 days ago
|
||
The patch landed in nightly and beta is affected.
:glandium, please make an uplift decision for beta:
- For beta, nominate the patch for beta uplift approval if the fix should be included in this release, or set
status-firefox161towontfixif the fix can wait for the next release.
Uplift requests can be submitted from Lando: D341201.
See Requesting an Uplift for documentation on how to request an uplift.
For more information, please visit BugBot documentation.
Updated•6 days ago
|
Updated•3 days ago
|
Description
•