CVE-2022-34881: Information Exposure Vulnerability in JP1/Automatic Operation
Noroxi assessment
Priority: Monitor (action score 13/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Hitachi JP1/Automatic Operation 11-51-09, 12-60-01.
Low priority for now. Upgrade to Hitachi JP1/Automatic Operation 11-51-09, 12-60-01 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Generation of Error Message Containing Sensitive Information vulnerability in Hitachi JP1/Automatic Operation allows local users to gain sensitive information. This issue affects JP1/Automatic Operation: from 10-00 through 10-54-03, from 11-00 before 11-51-09, from 12-00 before 12-60-01.
- Published
- Dec 5, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-209
Report tools
Action score
13
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 3.3
- CNA · Hitachi
- 3.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hitachi | jp1\/automatic operation | cpe:2.3:a:hitachi:jp1\/automatic_operation |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Hitachi). Independent of NVD's CPE analysis and usually ahead of it.
Hitachi JP1/Automatic Operation
- 10-00 and later · up to and including 10-54-03affected
- 11-00 and later · before 11-51-09affectedfixed in 11-51-09
- 12-00 and later · before 12-60-01affectedfixed in 12-60-01
- 10-52 and later · up to and including 10-54-03affected
- 11-00 and later · before 11-51-09affectedfixed in 11-51-09
- 12-00 and later · before 12-60-01affectedfixed in 12-60-01
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hitachi jp1/automatic operation11-12 and later · up to 11-12-03 inclusive
- hitachi jp1/automatic operation10-10 and later · up to 10-10-01 inclusive
- hitachi jp1/automatic operation10-12 and later · up to 10-12-05 inclusive
- hitachi jp1/automatic operation10-13 and later · up to 10-13-04 inclusive
- hitachi jp1/automatic operation10-52 and later · up to 10-52-05 inclusive
- hitachi jp1/automatic operation10-53 and later · up to 10-53-03 inclusive
- hitachi jp1/automatic operation10-54 and later · up to 10-54-03 inclusive
- hitachi jp1/automatic operation11-00 and later · up to 11-00-05 inclusive
- hitachi jp1/automatic operation11-01 and later · up to 11-01-03 inclusive
- hitachi jp1/automatic operation11-02 and later · up to 11-02-01 inclusive
- hitachi jp1/automatic operation11-10 and later · up to 11-10-07 inclusive
- hitachi jp1/automatic operation11-11 and later · up to 11-11-05 inclusive
- hitachi jp1/automatic operation11-12 and later · up to 11-12-04 inclusive
- hitachi jp1/automatic operation11-51 and later · up to 11-51-08 inclusive
- hitachi jp1/automatic operation12-00 and later · up to 12-00-01 inclusive
- hitachi jp1/automatic operation12-01 and later · up to 12-01-02 inclusive
- hitachi jp1/automatic operation12-10 and later · up to 12-10-02 inclusive
- hitachi jp1/automatic operation12-50 and later · up to 12-50-01 inclusive
- hitachi jp1/automatic operation11-10 and later · up to 11-10-06 inclusive
- hitachi jp1/automatic operation11-11 and later · up to 11-11-04 inclusive
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Hitachi JP1/Automatic Operation | 11-51-09 | Vendor (CNA) |
| Hitachi JP1/Automatic Operation | 12-60-01 | Vendor (CNA) |
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-209 · Generation of Error Message Containing Sensitive InformationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.