dbcve.org
Os 400Operating system · Ibm

CVE-2007-0442

MEDIUM · 5.0 CVSS v2.0 Published 2007-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 IBM OS/400 R530 and R535 has unknown impact and remote attack vectors, related to an "Integrity Problem" involving LIC-TCPIP and TCP reset. NOTE: it is possible that this issue is related to CVE-2004-0230, but this is not certain.

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

Vulnerability in IBM OS/400 R530 and R535 involving the LIC-TCPIP (Licensed Internal Code TCP/IP stack) component. Classified as an 'Integrity Problem' related to TCP reset packet handling. Possibly connected to CVE-2004-0230 which involved similar TCP reset vulnerabilities.

MitigationApply IBM PTFs (Program Temporary Fixes) specific to OS/400 R530/R535 addressing the LIC-TCPIP integrity issue. Consider upgrading to a supported IBM i version if patches are unavailable for these legacy releases.

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
Os 400Operating system
Affected:= r530= r535

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
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 checks

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

  1. Identify the OS/400 version
    Use the command to display system version information (such as DSPSYSINF or WRKSYSVAL) and locate the reported OS/400 release level
    Affected if The displayed version is R530 or R535 (specifically these two releases)
  2. Confirm LIC-TCPIP component is active
    Check if the TCP/IP stack component (LIC-TCPIP) is loaded and running on the system
    Affected if The LIC-TCPIP component is present and active on the system
  3. Verify TCP/IP stack is enabled
    Inspect the system configuration to confirm TCP/IP networking functionality is enabled
    Affected if TCP/IP is configured and operational on the OS/400 system

The system is affected if it is running OS/400 R530 or R535 with the LIC-TCPIP component enabled and TCP/IP stack active.

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 IBM PTFs (Program Temporary Fixes) specific to OS/400 R530/R535 addressing the LIC-TCPIP integrity issue. Consider upgrading to a supported IBM i version if patches are unavailable for these legacy releases.

Fix this in Os 400 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0442 — 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-0442 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