dbcve.org
Interstage Application Server EnterpriseApplication · Fujitsu

CVE-2008-2674

MEDIUM · 6.4 CVSS v2.0 Published 2008-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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
Unspecified vulnerability in the Interstage Management Console, as used in Fujitsu Interstage Application Server 6.0 through 9.0.0A, Apworks Modelers-J 6.0 through 7.0, and Studio 8.0.1 and 9.0.0, allows remote attackers to read or delete arbitrary files via unspecified 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

Arbitrary file read/delete vulnerability in Fujitsu Interstage Management Console affecting Application Server 6.0-9.0.0A, Apworks Modelers-J 6.0-7.0, and Studio 8.0.1/9.0.0. The vulnerability allows unauthenticated remote attackers to read or delete arbitrary files on the host system via unspecified vectors in the web-based management interface.

MitigationRestrict network access to the Interstage Management Console to trusted IPs only, or disable the console if not required. Contact Fujitsu for patches or consider upgrading to a supported version if available.

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
Interstage Application Server EnterpriseApplication
Affected:= v6.0= v7.0.0= v7.0.1= 8.0.0= 8.0.2= v9.0.0= 8.0.1= v7.0= 6.0= 7.0= 7.0.1= 9.0.0
Interstage Application Server PlusApplication
Affected:= v7.0.0= v7.0.1= 7.0= 7.0.1= v6.0= v7.0
Interstage Application Server Standard JApplication
Affected:= 8.0.0= 8.0.2= v9.0.0= 9.0.0= v9.0.0a
Interstage Application Server Plus DeveloperApplication
Affected:= v6.0= v7.0
Interstage Apworks Modelers JApplication
Affected:= v6.0= v6.0a= v7.0
Interstage Studio EnterpriseApplication
Affected:= 8.0.1= v9.0.0
Interstage Studio Standard JApplication
Affected:= 8.0.1= v9.0.0
Interstage Business Application Server EnterpriseApplication
Affected:= v8.0.0

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

AV:N/AC:L/Au:N/C:P/I:P/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 running Interstage Management Console service
    Check if the Interstage Management Console web service is running. Look for processes related to 'interstage' or 'management console', or check if ports typically used by the management console (often 80/443 or custom ports) are open and listening.
    Affected if The Interstage Management Console service is running and accessible on the network.
  2. Determine installed Interstage version
    Check the installed version of Fujitsu Interstage Application Server, Apworks Modelers-J, or Studio by reviewing installed software listings, product documentation, or version files. Common locations include installation directories or registry entries under Fujitsu/Interstage.
    Affected if The installed version matches one of the affected versions listed in the CVE (v6.0 through v9.0.0A across the various product lines).
  3. Verify management console network exposure
    Determine if the Interstage Management Console web interface is exposed to network access without authentication restrictions. Check firewall rules, network ACLs, or service binding configurations that control who can reach the management console port.
    Affected if The management console is reachable from untrusted network segments or the internet without IP restrictions.
  4. Confirm web-based management interface is enabled
    Inspect whether the web-based management console feature is actually enabled and functional. Check service configurations or startup parameters that control the management interface component.
    Affected if The web-based management interface is enabled and operational on the affected system.

A user is affected if they have any Fujitsu Interstage product (Application Server, Apworks Modelers-J, or Studio) running with the management console enabled and the installed version falls within the v6.0 to v9.0.0A range, especially if the console is accessible from untrusted networks.

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

Restrict network access to the Interstage Management Console to trusted IPs only, or disable the console if not required. Contact Fujitsu for patches or consider upgrading to a supported version if available.

Fix this in Interstage Application Server Enterprise 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-2008-2674 — 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-2008-2674 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