LiveActive security incident?Get immediate response
CVE Record

CVE-2023-37920: Certifi's removal of e-Tugra root certificate

Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi prior to version 2023.07.22 recognizes "e-Tugra" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from "e-Tugra" from the root store.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Certifi versions before 2023.07.22 trusted e-Tugra root certificates. Those roots were removed after public investigation into reported security issues at e-Tugra. Systems using affected Certifi versions may make TLS trust decisions using a root CA that Certifi no longer considers acceptable.

Executive priority

Treat this as a high-priority dependency hygiene issue, especially for systems relying on Python TLS validation. It is important, but the provided evidence does not support emergency active-exploitation handling.

Technical view

CVE-2023-37920 is a CWE-345 improper certificate validation issue in python-certifi versions >=2015.04.28 and <2023.07.22. The fix removes e-Tugra root certificates from Certifi’s CA bundle. CVSS is 7.5, driven by potential integrity impact over network TLS validation.

Likely exposure

Exposure is most likely in Python applications, containers, appliances, or packaged products using Certifi before 2023.07.22 for outbound TLS certificate validation.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Practical risk depends on whether affected systems trust certificates chaining to the removed e-Tugra roots.

Researcher notes

Evidence centers on CA trust-store removal, not a product exploit chain. Validate actual use of Certifi at runtime because many Python libraries depend on it indirectly. Do not assume exposure from package presence alone.

Mitigation direction

  • Update certifi to version 2023.07.22 or later.
  • Refresh lockfiles, containers, virtual environments, and packaged application bundles.
  • Check downstream vendor advisories for appliances or distributions that embed Certifi.
  • Prioritize systems handling sensitive outbound TLS connections.

Validation and detection

  • Inventory Certifi versions in SBOMs, lockfiles, images, and deployed Python environments.
  • Confirm affected assets no longer use Certifi versions before 2023.07.22.
  • Verify the deployed CA bundle no longer includes e-Tugra root certificates.
  • Review Fedora, NetApp, and other vendor advisories for inherited exposure.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-345: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-37920 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-37920Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
certifipython-certifi>= 2015.04.28, < 2023.07.22Listed
Weakness

CWE details

CWE-345

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-345 · source CWE mapping

Insufficient Verification of Data Authenticity

Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs