CyberSecBulletin
CVE-2023-3967NVD status: Modified

Hitachi Ops Center Common Services: Allocation of Resources Without Limits or Throttling

CVE-2023-3967 is a high-severity allocation of resources without limits or throttling vulnerability in Hitachi Ops Center Common Services from Hitachi, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 10.9.3-00 as the first without the flaw, so updating Hitachi Ops Center Common Services to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 51% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Hitachi Ops Center Common Services to 10.9.3-00 or a later version.
  2. Update ops_center_common_services to 10.9.3-00 or a later version.
  3. Read the advisory on hitachi.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
HitachiHitachi Ops Center Common Servicesbefore 10.9.3-0010.9.3-00
Hitachiops_center_common_servicesbefore 10.9.3-0010.9.3-00

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.15.3MediumCNA (hitachi.co.jp)
CVSS 3.17.5HighNVD

Official description

Allocation of Resources Without Limits or Throttling vulnerability in Hitachi Ops Center Common Services on Linux allows DoS.This issue affects Hitachi Ops Center Common Services: before 10.9.3-00.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How developers prevent this class of flaw

  • Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
  • Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Hitachi Ops Center Common Services

All Hitachi Ops Center Common Services vulnerabilities

Recent Allocation of Resources Without Limits or Throttling vulnerabilities

Spotted an error? Tell us.