Enhanced Support FacilityApplication · Fujitsu

CVE-2009-0867

MEDIUM · 5.0 CVSS v2.0 Published 2009-03-10
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
The HRM-S service in Fujitsu Enhanced Support Facility 3.0 and 3.0.1 allows remote attackers to obtain (1) hardware and (2) software information via unspecified requests in a client connection.

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 · high confidence

The HRM-S service in Fujitsu Enhanced Support Facility versions 3.0 and 3.0.1 exposes sensitive hardware and software inventory information to remote unauthenticated attackers via unspecified requests during client connections. This information disclosure could aid further attacks by revealing system configuration details.

MitigationUpgrade to a supported version of Fujitsu Enhanced Support Facility if available; otherwise, restrict network access to the HRM-S service using firewall rules or network segmentation to prevent unauthorized external access.

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
Enhanced Support FacilityApplication
Affected:= 3.0= 3.0.1

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
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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. Confirm Fujitsu Enhanced Support Facility is installed
    Check for the presence of Fujitsu Enhanced Support Facility software on the system - look for the application in installed programs or check for related processes/services
    Affected if The software is installed and running
  2. Identify the installed version
    Use system utility to view installed software version information for Fujitsu Enhanced Support Facility, or check the application's 'About' or version information
    Affected if The version is exactly 3.0 or 3.0.1
  3. Determine if HRM-S service is running
    Check running services or processes for HRM-S or related components of Fujitsu Enhanced Support Facility
    Affected if HRM-S service is active on the system
  4. Check network exposure of HRM-S service
    Review firewall rules, network configuration, or use network scanning to determine if the HRM-S service port is accessible from external network locations
    Affected if HRM-S service is reachable from remote unauthenticated network positions

A system is affected if Fujitsu Enhanced Support Facility versions 3.0 or 3.0.1 are installed with the HRM-S service running and exposed to unauthenticated network access.

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 a supported version of Fujitsu Enhanced Support Facility if available; otherwise, restrict network access to the HRM-S service using firewall rules or network segmentation to prevent unauthorized external access.

Fix this in Enhanced Support Facility Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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