Cobol Gui OptionApplication · Hitachi

CVE-2012-4274

HIGH · 10.0 CVSS v2.0 Published 2012-08-13
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 Cobol GUI Option 06-00, 06-01 through 06-01-/A, 07-00, 07-01 before 07-01-/B, and 08-00 before 08-00-/B and Cobol GUI Option Server 07-00, 07-01 before 07-01-/B, and 08-00 before 08-00-/B 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

This is an unspecified vulnerability in Hitachi Cobol GUI Option and Cobol GUI Option Server that allows remote attackers to execute arbitrary code via unknown attack vectors. The vulnerability affects multiple versions including 06-00, 06-01 through 06-01-/A, 07-00, 07-01 before 07-01-/B, and 08-00 before 08-00-/B. The critical severity (CVSS 10) indicates complete compromise of system confidentiality, integrity, and availability.

MitigationUpgrade Hitachi Cobol GUI Option to version 07-01-/B or 08-00-/B (or later) and Cobol GUI Option Server to the patched versions to remediate the remote code execution vulnerability.

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
Cobol Gui OptionApplication
Affected:= 06-00= 06-01= 06-01\/a= 07-00= 07-01= 07-01\/a= 08-00= 08-00\/a
Cobol Gui Option ServerApplication
Affected:= 07-00= 07-01= 07-01\/a= 08-00= 08-00\/a

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 if Hitachi Cobol GUI Option is installed
    Locate the Hitachi Cobol GUI Option installation directory or check system inventory for this product
    Affected if The product is present on the system
  2. Determine the version of Hitachi Cobol GUI Option
    Access the product's version information through its About dialog, version file, or installation logs
    Affected if The installed version is 06-00, 06-01, 06-01/A, 07-00, 07-01, 07-01/A, 08-00, or 08-00/A (versions before 07-01-/B or 08-00-/B)
  3. Identify if Hitachi Cobol GUI Option Server is installed
    Locate the Cobol GUI Option Server component or check system inventory for this server product
    Affected if The server component is present on the system
  4. Determine the version of Hitachi Cobol GUI Option Server
    Access the server component's version information through its About dialog, version file, or installation logs
    Affected if The installed version is 07-00, 07-01, 07-01/A, 08-00, or 08-00/A (versions before the patched releases)
  5. Verify if the vulnerability is exploitable
    Confirm that the affected product is configured and running with network exposure or remote access enabled
    Affected if The vulnerable version is actively running and accessible to remote attackers

The environment is affected if either Hitachi Cobol GUI Option or Cobol GUI Option Server is installed with a version matching 06-00 through 08-00/A (excluding the patched 07-01-/B and 08-00-/B releases).

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 Hitachi Cobol GUI Option to version 07-01-/B or 08-00-/B (or later) and Cobol GUI Option Server to the patched versions to remediate the remote code execution vulnerability.

Fix this in Cobol Gui Option Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-4274 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