Buffer overflow in Hitachi Cosminexus V4 through V7, Processing Kit for XML before 20070511, Developer's Kit for Java before 20070312, and t
Buffer overflow in Hitachi Cosminexus V4 through V7, Processing Kit for XML before 20070511, Developer's Kit for Java before 20070312, and third-party products that use this software, allows attackers to have an unknown impact via certain GIF images, related to use of GIF image processing APIs by a Java application.
- Published
- Jul 15, 2007
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
41
Plan
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| hitachi | cosminexus application server | cpe:2.3:a:hitachi:cosminexus_application_server |
| hitachi | cosminexus client | cpe:2.3:a:hitachi:cosminexus_client |
| hitachi | cosminexus developer | cpe:2.3:a:hitachi:cosminexus_developer |
| hitachi | cosminexus server | cpe:2.3:a:hitachi:cosminexus_server |
| hitachi | cosminexus studio | cpe:2.3:a:hitachi:cosminexus_studio |
| hitachi | ucosminexus application server | cpe:2.3:a:hitachi:ucosminexus_application_server |
| hitachi | ucosminexus client | cpe:2.3:a:hitachi:ucosminexus_client |
| hitachi | ucosminexus developer | cpe:2.3:a:hitachi:ucosminexus_developer |
| hitachi | ucosminexus operator | cpe:2.3:a:hitachi:ucosminexus_operator |
| hitachi | ucosminexus service architect | cpe:2.3:a:hitachi:ucosminexus_service_architect |
| hitachi | ucosminexus service platform | cpe:2.3:a:hitachi:ucosminexus_service_platform |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hitachi cosminexus application server05_00_05_00_h
- hitachi cosminexus application server05_00_05_00_r
- hitachi cosminexus application server05_01_05_01_k
- hitachi cosminexus application server05_02_05_02_e
- hitachi cosminexus application server05_05_05_00_o
- hitachi cosminexus application server05_05_05_05_h
- hitachi cosminexus application server05_05_05_05_l
- hitachi cosminexus application server06_00_06_00_a
- hitachi cosminexus application server06_00_06_00_b
- hitachi cosminexus application server06_00_06_00_d
- hitachi cosminexus application server06_00_06_00_e
- hitachi cosminexus application server06_00_06_00_g
- hitachi cosminexus application server06_02_06_02_f
- hitachi cosminexus application server06_50_06_50_b
- hitachi cosminexus application server06_50_06_50_c
- hitachi cosminexus application server06_50_06_50_d
- hitachi cosminexus application server06_50_06_50_e
- hitachi cosminexus application server06_50_06_50_f
- hitachi cosminexus application server06_51_06_51_b
- hitachi cosminexus application server06_51_06_51_c
Same product
hitachi: all recordsOther highest-scoring records for the same primary product.
- CVE-2007-3626Unspecified vulnerability in the ADM daemon in Hitachi TPBroker before 20070706 allows remote attackers to cause a denial of service (daemon32Monitor
- CVE-2007-0514Multiple cross-site scripting (XSS) vulnerabilities in multiple Hitachi Web Server, uCosminexus, and Cosminexus products before 20070124 all27Monitor
- CVE-2007-4124The session failover function in Cosminexus Component Container in Cosminexus 6, 6.7, and 7 before 20070731, as used in multiple Hitachi pro19Monitor
- CVE-2005-3164The AJP connector in Apache Tomcat 4.0.1 through 4.0.6 and 4.1.0 through 4.1.36, as used in Hitachi Cosminexus Application Server and standa12Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- osvdb.org/37851
- secunia.com/advisories/26025
- www.hitachi-support.com/security_e/vuls_e/HS07-018_e/index-e.html
- www.securityfocus.com/bid/24905
- www.vupen.com/english/advisories/2007/2534
Vendor advisories and official records. Exploit/PoC links are deliberately left out.