dbcve.org
AixOperating system · Ibm

CVE-2013-3035

HIGH · 7.1 CVSS v2.0 Published 2013-06-21
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
The IPv6 implementation in the inet subsystem in IBM AIX 6.1 and 7.1, and VIOS 2.2.2.2-FP-26 SP-02, allows remote attackers to cause a denial of service (system hang) via a crafted packet to an IPv6 interface.

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

A denial of service vulnerability exists in the IPv6 implementation within the inet subsystem of IBM AIX 6.1, AIX 7.1, and VIOS 2.2.2.2. Remote attackers can send a specially crafted IPv6 packet to an IPv6-enabled interface, causing the system to hang or become unresponsive.

MitigationIf IPv6 is not required, disable it on affected systems. Otherwise, filter or block untrusted IPv6 traffic at network boundaries until vendor patches can be applied.

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
AixOperating system
Affected:= 6.1= 7.1
ViosOperating system
Affected:= 2.2.1.4

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. Identify AIX or VIOS version
    Run 'oslevel -s' on AIX or 'oem_platform_level' on VIOS to get the exact version number. For AIX 6.1, look for versions starting with 6100-. For AIX 7.1, look for versions starting with 7100-. For VIOS, check if version is 2.2.1.4.
    Affected if The system is running AIX 6.1.x, AIX 7.1.x, or VIOS 2.2.1.4.
  2. Verify IPv6 is enabled
    Run 'lsattr -El inet0' and look for 'ipv6' in the output. A value of 'true' indicates IPv6 is enabled.
    Affected if IPv6 is enabled (ipv6 attribute set to true).
  3. Check for active IPv6 interfaces
    Run 'ifconfig -a' and look for inet6 addresses (entries starting with 'inet6').
    Affected if Any interface has an IPv6 address assigned, indicating IPv6 is actively in use.
  4. Confirm inet0 stack status
    Run 'lsattr -El inet0' and check that the 'inet0' interface is in a 'ready' or 'available' state.
    Affected if The inet0 interface is available and IPv6 is not disabled at the stack level.

A system is affected if it runs AIX 6.1.x, AIX 7.1.x, or VIOS 2.2.1.4 AND has IPv6 enabled at the inet0 level, regardless of whether any interface has an active IPv6 address.

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

If IPv6 is not required, disable it on affected systems. Otherwise, filter or block untrusted IPv6 traffic at network boundaries until vendor patches can be applied.

Fix this in Aix 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-2013-3035 — 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-2013-3035 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