CVE-2010-4038 json
The Web Sockets implementation in Google Chrome before 7.0.517.41 does not properly handle a shutdown action, which allows remote attackers…
published 16y ago modified 4mo ago also EUVD-2010-4014
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
The Web Sockets implementation in Google Chrome before 7.0.517.41 does not properly handle a shutdown action, which allows remote attackers to cause a denial of service (application crash) via unspecified vectors.
Patch / fix
- google chrome 7.0.517.41
Is CVE-2010-4038 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.67% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- code.google.com http://code.google.com/p/chromium/issues/detail?id=53985 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-404 Improper Resource Shutdown or Release
- Technology feeds
References
-
code.google.com
/p/chromium/issues/detail?id=53985
exploit, issue-tracking, mailing-list, vendor-advisory
-
googlechromereleases.blogspot.com
/2010/10/stable-channel-update.html
release-notes, vendor-advisory
-
vupen.com
/english/advisories/2010/2731
vdb-entry, not-applicable
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A13930
vdb-entry, signature, third-party-advisory
-
secunia.com
/advisories/41888
third-party-advisory, broken-link
-
securityfocus.com
/bid/44241
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2010-4038
- NVD CVE-2010-4038
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.