CVE-2002-1755
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 · uneditedtinc 1.0pre3 and 1.0pre4 VPN does not authenticate forwarded packets, which allows remote attackers to inject data into user sessions without detection, and possibly control the data contents via cut-and-paste attacks on CBC.
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 confidencetinc VPN versions 1.0pre3 and 1.0pre4 fail to authenticate forwarded packets, allowing remote attackers to inject arbitrary data into active VPN sessions without detection. The lack of authentication also enables cut-and-paste attacks on CBC-encrypted data, potentially allowing adversaries to manipulate ciphertext and control decrypted content.
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= 1.0pre3= 1.0pre4CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 tinc installationRun 'tinc --version' or check the package manager (dpkg -l tinc, rpm -q tinc) to determine the installed tinc versionAffected if Version displayed is 1.0pre3 or 1.0pre4
-
Check tinc binary version stringIf tinc is installed, execute the binary with version flag or inspect the binary metadata: 'tincd --version' or check /usr/sbin/tincd versionAffected if Binary reports version 1.0pre3 or 1.0pre4
-
Verify tinc configuration directoryLocate the tinc configuration directory (commonly /etc/tinc or /etc/tinc/VPNNAME) and check for any version indication files or scriptsAffected if Configuration files reference or bundle tinc version 1.0pre3 or 1.0pre4
-
Inspect packet authentication configurationExamine tinc.conf for 'digest' or 'authphase' options - affected versions lack packet authentication, so absence of these options indicates vulnerable state in affected versionsAffected if Running 1.0pre3 or 1.0pre4 AND no packet authentication (digest) is configured in tinc.conf
If the installed tinc version is exactly 1.0pre3 or 1.0pre4, the environment is vulnerable to unauthenticated packet injection and CBC ciphertext manipulation.
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 dataUpgrade to a patched version of tinc that implements proper packet authentication and integrity verification. If upgrading is not immediately feasible, restrict network access to trusted peers and monitor for anomalous traffic patterns.
- Consultation2.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1755 — 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-2002-1755 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