dbcve.org
LinkoneApplication · Hitachi

CVE-2021-40338

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Hitachi Energy LinkOne product, has a vulnerability due to a web server misconfiguration, that enables debug mode and reveals the full path of the filesystem directory when an attacker generates errors during a query operation. This issue affects: Hitachi Energy LinkOne 3.20; 3.22; 3.23; 3.24; 3.25; 3.26.

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 Energy LinkOne contains a web server misconfiguration that enables debug mode, causing the application to reveal full filesystem directory paths in verbose error messages when query operations generate errors. This information disclosure could aid attackers in mapping the system architecture for further exploitation.

MitigationDisable debug mode in the web server configuration and implement custom error handling that returns generic error messages without exposing filesystem paths. Review and test the error handling to confirm paths are no longer disclosed.

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
LinkoneApplication
Affected:= 3.20= 3.22= 3.23= 3.24= 3.25= 3.26

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify installed LinkOne version
    Check the application's version information through its about dialog, installation directory, or by querying the web server banner if exposed. Look for version files or check the product information interface.
    Affected if The installed version matches 3.20, 3.22, 3.23, 3.24, 3.25, or 3.26 exactly.
  2. Locate web server configuration files
    Find the web server configuration files used by LinkOne, typically named httpd.conf, web.config, or similar, located in the application's config or web server root directory.
    Affected if Debug mode settings are found and enabled in the web server configuration.
  3. Verify debug mode setting in configuration
    Open the web server configuration file and search for debug-related directives such as 'Debug', 'Trace', 'VerboseErrors', or similar settings that enable detailed error reporting.
    Affected if A directive enabling debug, trace, or verbose error output is set to true, on, or enabled.
  4. Test error message disclosure
    Send a malformed or invalid query request to the LinkOne web interface and capture the full error response. Look for directory paths, file paths, or stack traces in the returned error page.
    Affected if The error response contains absolute filesystem paths, directory structures, or detailed stack traces rather than generic error messages.
  5. Inspect custom error handler configuration
    Review the web server or application error handling configuration to determine if custom error pages are defined and whether they mask filesystem paths.
    Affected if No custom error handlers are defined, or existing handlers still expose filesystem paths in their output.

A user is affected if they run any of the exact versions 3.20, 3.22, 3.23, 3.24, 3.25, or 3.26 and the web server debug mode is enabled, resulting in filesystem path disclosure in error responses.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable debug mode in the web server configuration and implement custom error handling that returns generic error messages without exposing filesystem paths. Review and test the error handling to confirm paths are no longer disclosed.

Recommended fix Moderate confidence
  1. Access the LinkOne web server configuration files (typically found in the web server's conf directory or within the LinkOne application configuration)
  2. Locate the debug mode setting in the web server configuration (often labeled as 'debug', 'Debug', or 'allowDebug')
  3. Set the debug mode parameter to 'false' or 'disabled' to turn off debug functionality
  4. Restart the LinkOne web server service to apply the configuration changes
  5. Verify the fix by intentionally triggering error conditions through query operations and confirming that full filesystem paths are no longer exposed in error messages

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linkone Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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