dbcve.org
Cobol2002 Net DeveloperApplication · Hitachi

CVE-2012-0918

HIGH · 10.0 CVSS v2.0 Published 2012-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 COBOL2002 Net Developer, Net Server Suite, and Net Client Suite 01-00, 01-01 through 01-01-/D, 01-02 through 01-02-/F, 01-03 through 01-03-/F, 02-00 through 02-00-/D, 02-01 through 02-01-/C, and possibly other versions before 02-01-/D allows remote attackers to execute arbitrary code via unknown attack 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 · moderate confidence

Hitachi COBOL2002 Net Developer, Net Server Suite, and Net Client Suite contain an unspecified vulnerability allowing remote attackers to execute arbitrary code via unknown vectors. The CVSS 10 score indicates this is a remotely exploitable, unauthenticated RCE with complete impact to confidentiality, integrity, and availability.

MitigationUpgrade to version 02-01-/D or later to remediate. If immediate patching is not feasible, isolate affected systems behind network segmentation and restrict external access to COBOL services.

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
Cobol2002 Net DeveloperApplication
Affected:= 01-00= 01-01= 01-01-\/d= 01-02= 01-02-\/f= 01-03= 01-03-\/f= 02-00= 02-00-\/d= 02-01= 02-01-\/c
Cobol2002 Net Server SuiteApplication
Affected:= 01-00= 01-01= 01-01-\/d= 01-02= 01-02-\/f= 01-03= 01-03-\/f= 02-00= 02-00-\/d= 02-01
Cobol2002 Net Client SuiteApplication
Affected:= 01-00= 01-01= 01-01-\/d= 01-02= 01-02-\/f= 01-03= 01-03-\/f= 02-00= 02-00-\/d= 02-01

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
Complete
Integrity
Complete
Availability
Complete

AV:N/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 checks

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

  1. Identify installed Hitachi COBOL2002 product
    Check the system for installation of Hitachi COBOL2002 Net Developer, Net Server Suite, or Net Client Suite. Look in Program Files for Hitachi COBOL2002 directories, or check Windows Registry under HKLM\Software\Hitachi or similar paths.
    Affected if Any of the three COBOL2002 product suites are found installed on the system
  2. Determine the exact product version
    Locate the version information for the installed product. Check the program directory for version files, or use the application's About/Version dialog if accessible. Common paths include C:\Program Files\Hitachi\COBOL2002\ or version info embedded in executable properties.
    Affected if The installed version matches one of the affected versions: 01-00, 01-01, 01-01-/d, 01-02, 01-02-/f, 01-03, 01-03-/f, 02-00, 02-00-/d, or 02-01 for any of the three product suites
  3. Compare against fixed version
    Identify the full version string including any subversion designators (such as /d, /f suffixes). The fixed version is 02-01-/D.
    Affected if The installed version is 02-01 or any version prior to 02-01-/D (including all 01-xx and 02-00 versions)
  4. Verify network exposure of COBOL services
    Check if COBOL2002 services are listening on network ports or accessible from external interfaces. Review firewall rules and service configurations for Net Server Suite or Net Client components.
    Affected if COBOL2002 services are exposed to network access, especially unauthenticated external access

The system is affected if any version of Hitachi COBOL2002 Net Developer, Net Server Suite, or Net Client Suite matching 01-00 through 02-01 is installed, particularly if the version is below 02-01-/D and the service is network-accessible.

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

Upgrade to version 02-01-/D or later to remediate. If immediate patching is not feasible, isolate affected systems behind network segmentation and restrict external access to COBOL services.

Fix this in Cobol2002 Net Developer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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