dbcve.org
Tpi Server BaseApplication · Hitachi

CVE-2007-3795

HIGH · 7.1 CVSS v2.0 Published 2007-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in Hitachi TP1/Server Base before 03-05-/P, 05-00-x before 05-00-/G, 05-01-x before 05-01-/A, and 05-02-x before 05-02-/C on HP-UX 11.0 through 11i v3 allows attackers to cause a denial of service by sending certain data to a port.

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 confidence

Hitachi TP1/Server Base on HP-UX 11.0 through 11i v3 contains an unspecified vulnerability that allows remote attackers to cause a denial of service by sending specially crafted data to a specific port. The vulnerability affects multiple version branches (03-05-x, 05-00-x, 05-01-x, 05-02-x) prior to their respective security patch releases.

MitigationApply the vendor-supplied patches (03-05-/P, 05-00-/G, 05-01-/A, or 05-02-/C depending on version branch) to resolve the vulnerability. If patches are unavailable, consider network segmentation to limit exposure to the affected port.

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
Tpi Server BaseApplication
Affected:= 03_03_d= 03_04_j= 03_05_f= 03_05_o= 05_00= 05_00_f= 05_01= 05_02= 05_02_b

CVSS 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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/Au:N/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify HP-UX version
    Run 'uname -a' or 'swlist -l product HP-UX' to confirm the system is HP-UX 11.0 through 11i v3
    Affected if System is running HP-UX outside the 11.0 to 11i v3 range (not affected)
  2. Check if Hitachi TP1/Server Base is installed
    Run 'swlist -l product | grep -i tpi' or 'swlist -l product | grep -i serverbase' to identify if Hitachi TP1/Server Base is present
    Affected if Hitachi TP1/Server Base is not installed (not affected)
  3. Identify installed Hitachi TP1/Server Base version
    Run 'swlist -l product <product_name>' substituting the product name found in the previous step, or check /var/adm/sw/products for the installed version string
    Affected if Version matches one of the vulnerable versions: 03_03_d, 03_04_j, 03_05_f, 03_05_o, 05_00, 05_00_f, 05_01, 05_02, or 05_02_b
  4. Verify the service is running and exposed
    Check if the Hitachi TP1/Server Base service is actively running and bound to a network interface using 'netstat -an | grep <port>' or 'ps -ef | grep tpi' - the specific port should be determined based on the service configuration
    Affected if The service is not running or not network-exposed (lower risk)
  5. Confirm no security patches applied
    Run 'swlist -l patch | grep -i tpi' or check /var/adm/sw/patches for patches matching the version branch (03-05, 05-00, 05-01, or 05-02)
    Affected if No corresponding security patch (03-05-/P, 05-00-/G, 05-01-/A, or 05-02-/C) has been installed for the version branch

The environment is affected if running HP-UX 11.0-11i v3 with any installed Hitachi TP1/Server Base version matching 03_03_d, 03_04_j, 03_05_f, 03_05_o, 05_00, 05_00_f, 05_01, 05_02, or 05_02_b without the corresponding security patch applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches (03-05-/P, 05-00-/G, 05-01-/A, or 05-02-/C depending on version branch) to resolve the vulnerability. If patches are unavailable, consider network segmentation to limit exposure to the affected port.

Fix this in Tpi Server Base Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-3795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-3795 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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