dbcve.org
TgtApplication · Zaal

CVE-2010-2221

MEDIUM · 5.0 CVSS v2.0 Published 2010-07-08
Fix available
A fix is available. Upgrade to after 1.4.20 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Multiple buffer overflows in the iSNS implementation in isns.c in (1) Linux SCSI target framework (aka tgt or scsi-target-utils) before 1.0.6, (2) iSCSI Enterprise Target (aka iscsitarget or IET) 1.4.20.1 and earlier, and (3) Generic SCSI Target Subsystem for Linux (aka SCST or iscsi-scst) 1.0.1.1 and earlier allow remote attackers to cause a denial of service (memory corruption and daemon crash) or possibly execute arbitrary code via (a) a long iSCSI Name string in an SCN message or (b) an invalid PDU.

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 · high confidence

Multiple buffer overflow vulnerabilities exist in the iSNS (iSCSI Storage Networking) implementation across three major Linux SCSI target frameworks: tgt, IET, and SCST. The vulnerabilities are triggered by processing a long iSCSI Name string in an SCN (State Change Notification) message or an invalid PDU (Protocol Data Unit), leading to heap or stack buffer overflows. This can result in memory corruption, daemon crash (denial of service), or potentially arbitrary code execution by remote attackers.

MitigationUpgrade to patched versions of the affected software (tgt 1.0.6+, IET post-1.4.20.1, SCST post-1.0.1.1) or apply vendor-provided security patches. Additionally, restrict network access to iSNS ports (3205, 3206) to trusted sources to reduce attack surface.

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
TgtApplication
Affected:<= 1.0.5= 0.9.5= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4
IscsitargetApplication
Affected:<= 1.4.20= 0.1.0= 0.2.0= 0.2.1= 0.2.2= 0.2.3= 0.2.4= 0.2.5= 0.2.6= 0.3.0= 0.3.1= 0.3.2
Generic Scsi Target SubsystemApplication
Affected:<= 1.0.1= 0.9.0a= 0.9.1= 0.9.2= 0.9.3= 0.9.4= 0.9.5= 0.9.5.1= 0.9.5.2= 1.0.0

CVSS 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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if tgt daemon is installed
    Run 'dpkg -l | grep tgt' or 'rpm -qa | grep tgt' or check for /usr/sbin/tgtd
    Affected if tgt version is 0.9.5, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, or 1.0.5 (or any version <= 1.0.5)
  2. Identify if iscsitarget (IET) is installed
    Run 'dpkg -l | grep iscsitarget' or 'rpm -qa | grep iscsitarget' or check for /usr/sbin/ietd
    Affected if iscsitarget version is 0.1.0, 0.2.0 through 0.2.6, 0.3.0 through 0.3.2, or 1.4.20 (or any version <= 1.4.20)
  3. Identify if SCST is installed
    Run 'modprobe -l | grep scst' or check for /proc/scsi_tgt/scst_version, or run 'scstadmin -version' if available
    Affected if SCST version is 0.9.0a, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.5.1, 0.9.5.2, 1.0.0, or 1.0.1 (or any version <= 1.0.1)
  4. Verify iSNS service is enabled
    Check if ietd or tgtd is configured to listen on ports 3205 or 3206 (iSNS), or review /etc/iet/ietd.conf or /etc/tgt/targets.conf for iSNS settings
    Affected if The iSCSI target daemon has iSNS protocol support enabled and is listening on iSNS ports
  5. Check for remote access to iSNS ports
    Run 'netstat -tlnp | grep -E "3205|3206"' or 'ss -tlnp | grep -E "3205|3206"' to see if ports 3205/tcp or 3206/tcp are open
    Affected if Ports 3205 or 3206 are bound to a daemon and accessible from untrusted network segments

The environment is affected if any of tgt (version <= 1.0.5), iscsitarget/IET (version <= 1.4.20), or SCST (version <= 1.0.1) is installed with iSNS enabled and accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 1.4.20
Interim mitigation

Upgrade to patched versions of the affected software (tgt 1.0.6+, IET post-1.4.20.1, SCST post-1.0.1.1) or apply vendor-provided security patches. Additionally, restrict network access to iSNS ports (3205, 3206) to trusted sources to reduce attack surface.

Fix this in Tgt Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-2221 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-2221 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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