Skip to content
Fencer Intel
medium 5.0

CVE-2010-2621 json

The QSslSocketBackendPrivate::transmit function in src_network_ssl_qsslsocket_openssl.cpp in Qt 4.6.3 and earlier allows remote attackers t…

published 16y ago modified 4mo ago also EUVD-2010-2625

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.5%
EPSS 10.5% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

The QSslSocketBackendPrivate::transmit function in src_network_ssl_qsslsocket_openssl.cpp in Qt 4.6.3 and earlier allows remote attackers to cause a denial of service (infinite loop) via a malformed request.

Patch / fix

Is CVE-2010-2621 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 Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-2621 updated cvss 4.3

(QSslSocketBackendPrivate): DoS (infinite loop) via malformed request

  • Red Hat Enterprise Linux 6 qt, qt-x11, qt-odbc, qt-demos, qt-mysql, qt-sqlite, +3 more
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-14268)

Exploit prediction

10.54% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-14268 Qt 4.6.3 - 'QSslSocketBackendPrivate::transmit()' Denial of Service dos, 2010-07-08
  • aluigi.org http://aluigi.org/poc/qtsslame.zip referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/41250 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

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.