CVE-2003-1360
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 · uneditedBuffer overflow in the setupterm function of (1) lanadmin and (2) landiag programs of HP-UX 10.0 through 10.34 allows local users to execute arbitrary code via a long TERM environment variable.
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 confidenceBuffer overflow vulnerability in the setupterm function of HP-UX lanadmin and landiag utilities allows local attackers to execute arbitrary code via a specially crafted long TERM environment variable. The overflow occurs when the program processes the TERM variable without proper bounds checking.
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= 10.00= 10.01= 10.08= 10.09= 10.10= 10.16= 10.20= 10.24= 10.26= 10.30= 10.34CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check HP-UX versionRun 'uname -a' or 'swlist -l product | grep -i hpux' to identify the installed HP-UX versionAffected if The version is any of: 10.00, 10.01, 10.08, 10.09, 10.10, 10.16, 10.20, 10.24, 10.26, 10.30, or 10.34
-
Verify lanadmin utility existsRun 'which lanadmin' or 'ls -la /usr/sbin/lanadmin' to locate the lanadmin binaryAffected if lanadmin is found on the system and HP-UX version is 10.x from the affected list
-
Verify landiag utility existsRun 'which landiag' or 'ls -la /usr/sbin/landiag' to locate the landiag binaryAffected if landiag is found on the system and HP-UX version is 10.x from the affected list
-
Check TERM environment variableRun 'echo $TERM' to see the current TERM variable settingAffected if TERM is set to any value, especially long or unexpected values that could trigger the overflow when lanadmin or landiag is executed
A system is affected if it runs HP-UX version 10.00-10.34 and has lanadmin or landiag utilities installed, as the buffer overflow triggers when these utilities process the TERM environment variable.
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 dataHP-UX 10.x is end-of-life and no longer receives security patches. Recommended remediation is to migrate to a supported HP-UX version (11i v3 or later) or decommission these legacy systems. As an interim workaround, restrict local access to systems running these utilities and avoid using them with untrusted TERM environment variables.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-1360 — 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-2003-1360 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