CVE-2011-3168
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 · uneditedUnspecified vulnerability in the POP and IMAP service implementations in HP TCP/IP Services 5.6 and 5.7 for OpenVMS allows remote attackers to obtain sensitive information via unknown vectors.
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 · low confidenceMemory disclosure vulnerability in HP TCP/IP Services for OpenVMS POP3/IMAP daemons allows remote attackers to obtain sensitive information via unspecified vectors.
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= 5.6= 5.7CVSS 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.
-
Verify OpenVMS operating systemUse the OpenVMS command $ SHOW SYSTEM or $ VERIFY to confirm the system is running OpenVMSAffected if System is running OpenVMS as the operating system
-
Confirm HP TCP/IP Services installationRun $ SHOW PRODUCT to list installed products and check for HP TCP/IP Services (product name typically TCPIP)Affected if HP TCP/IP Services for OpenVMS is installed on the system
-
Identify the TCP/IP Services versionUse $ SHOW PRODUCT TCPIP to display the installed version; compare the version number against the affected versions 5.6 and 5.7Affected if Version is exactly 5.6 or 5.7
-
Check if POP3 service is enabledRun TCPIP SHOW SERVICE POP3 to see if the POP3 daemon is configured; verify the service status shows as enabled or runningAffected if POP3 service (port 110) is enabled and running on the system
-
Check if IMAP service is enabledRun TCPIP SHOW SERVICE IMAP to see if the IMAP daemon is configured; verify the service status shows as enabled or runningAffected if IMAP service (port 143) is enabled and running on the system
System is affected if it runs OpenVMS with HP TCP/IP Services version 5.6 or 5.7 and has POP3 or IMAP services enabled and accessible.
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 dataRestrict network access to POP (port 110) and IMAP (port 143) services to trusted IPs only; monitor for anomalous access patterns; contact HP for available patches or updated versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3168 — 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-2011-3168 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