CVE-2024-0310
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA content-security-policy vulnerability in ENS Control browser extension prior to 10.7.0 Update 15 allows a remote attacker to alter the response header parameter setting to switch the content security policy into report-only mode, allowing an attacker to bypass the content-security-policy configuration.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe ENS Control browser extension before version 10.7.0 Update 15 contains a content-security-policy vulnerability where remote attackers can manipulate response headers to switch CSP from enforced mode to report-only mode. This disables CSP protections and allows attackers to bypass restrictions for XSS, data injection, and other client-side attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.7.0= 10.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate ENS Control browser extension versionIn Chrome, go to chrome://extensions and enable Developer Mode, then find the ENS Control or Trellix Endpoint Security Web Control extension to view its version number. In Firefox, go to about:addons and find the extension in the list.Affected if installed version is less than 10.7.0 Update 15, or is exactly version 10.7.0 without the Update 15 patch applied
-
Verify extension version in Trellix management consoleLog into the Trellix ePolicy Orchestrator (ePO) or central management console and search for the ENS Control extension deployment status to confirm the exact version number deployed.Affected if deployed version shows as any version before 10.7.0 Update 15 or shows 10.7.0 without the Update 15 notation
-
Confirm CSP enforcement status in browserOpen browser developer tools (F12), go to the Security tab, and inspect whether Content-Security-Policy is reported as enforced or report-only for pages loaded while ENS Control is active.Affected if CSP shows as report-only mode when it should be enforced, indicating possible manipulation of CSP headers by the vulnerable extension
You are affected if the ENS Control browser extension version is any version before 10.7.0 Update 15, or is exactly 10.7.0 without the Update 15 patch applied.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.7.0
Upgrade to ENS Control browser extension version 10.7.0 Update 15 or later, which should contain the fix for preventing CSP header manipulation.
10.7.0 Update 15
- Navigate to the Trellix Endpoint Security management console
- Locate the Web Control component or browser extension settings
- Check the current version of ENS Control browser extension
- If the version is below 10.7.0 Update 15, initiate an update to version 10.7.0 Update 15 or later
- Verify the update was successfully applied by checking the version number post-update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0310 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data