CVE-2006-6171: n/a vulnerability

CVE-2006-6171: ProFTPD 1.3.0a and earlier does not properly set the buffer size limit when CommandBufferSize is specified...

ProFTPD 1.3.0a and earlier does not properly set the buffer size limit when CommandBufferSize is specified in the configuration file, which leads to an off-by-two buffer underflow. NOTE: in November 2006, the role of CommandBufferSize was originally associated with CVE-2006-5815, but this was an error stemming from a vague initial disclosure. NOTE: ProFTPD developers dispute this issue, saying that the relevant memory location is overwritten by assignment before further use within the affected function, so this is not a vulnerability

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 20:19 UTC (UTC+00:00)

Security readout for executives and security teams

This is an old, disputed ProFTPD issue involving CommandBufferSize handling. The record says ProFTPD 1.3.0a and earlier may have an off-by-two buffer underflow, but ProFTPD developers disputed that it is exploitable because the relevant memory is overwritten before further use. Exposure is most plausible on legacy ProFTPD 1.3.0a or earlier systems where CommandBufferSize is set. The source bundle does not identify current supported products, CPEs, or confirmed vulnerable distribution package versions. Treat this as a legacy hygiene item unless asset inventory shows exposed, obsolete ProFTPD. The business risk is unclear because severity and exploitability are not established, but unsupported internet-facing FTP should still be prioritized for replacement or upgrade. Mitigation focus: Check ProFTPD and distribution advisories for package-specific guidance.; Upgrade unsupported ProFTPD installations through vendor-supported packages.; Review configurations for CommandBufferSize usage on legacy systems..

Prepared: Jun 29, 2026, 09:12 UTC (UTC+00:00)

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.

cve · low confidence lookup

CVE-2006-6171 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: Unknown
CVSS: Not scored
Known Exploited: No
Published: Nov 30, 2006, 15:00 UTC (UTC+00:00)

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.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214820CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

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