CVE-2006-1644
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 · uneditedlogin.php in Interact 2.1.1 generates different responses depending on whether or not a username is valid, which allows remote attackers to determine valid usernames. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 login.php script in Interact version 2.1.1 exhibits different behavior depending on whether a submitted username exists in the system. This allows remote attackers to perform username enumeration by observing the varying responses (such as different error messages or timing differences) when attempting to authenticate with valid versus invalid usernames.
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<= 2.1.1= 1.8.7= 1.9= 1.9.1= 2.0= 2.1CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Identify Interact installation and versionLocate the Interact web application files and check for version indicators such as a version file, header comments in PHP files, or configuration files that may contain version informationAffected if The installed version matches any of the following: 1.8.7, 1.9, 1.9.1, 2.0, 2.1, or 2.1.1 (or any version <= 2.1.1)
-
Verify login.php existsCheck for the presence of login.php in the web-accessible directory of the Interact installationAffected if login.php is present and accessible via web request
-
Test authentication response for valid usernameSubmit a login request to login.php with a known-valid username (or test with several common usernames) and a random password, then record the error message and response behaviorAffected if The response indicates that the username exists (for example, an error message stating the password is incorrect rather than that the user does not exist)
-
Test authentication response for invalid usernameSubmit a login request to login.php with a clearly invalid username (such as a random string that would not be a real user) and any password, then record the error message and response behaviorAffected if The response indicates that the username does not exist (for example, an error message stating the user was not found)
-
Compare responses for enumeration vulnerabilityCompare the error messages and timing from step 3 and step 4 - if they differ in content or response time, the vulnerability is presentAffected if The login.php script returns different error messages or shows noticeably different response times between valid and invalid usernames, allowing an attacker to determine which usernames are registered in the system
A defender is affected if the Interact version is 1.8.7, 1.9, 1.9.1, 2.0, 2.1, or 2.1.1 (or any version <= 2.1.1) AND the login.php script returns distinguishable responses for valid versus invalid usernames.
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.
From vendor dataModify the login.php script to return identical error messages and response times regardless of whether the provided username exists in the system, preventing user enumeration.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1644 — 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-2006-1644 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