CVE-2024-53855
Published: 27 November 2024
Summary
CVE-2024-53855 is a low-severity Improper Isolation or Compartmentalization (CWE-653) vulnerability in Nofusscomputing Centurion Erp. Its CVSS base score is 1.9 (Low).
Operationally, ranked at the 49.4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52176
Vulnerability details
Centurion ERP (Enterprise Rescource Planning) is a simple application developed to provide open source IT management with a large emphasis on the IT Service Management (ITSM) modules. A user who is authenticated and has view permissions for a ticket, can…
more
view the tickets of another organization they are not apart of. Users with following permissions are applicable: 1. `view_ticket_change` permission can view change tickets from organizations they are not apart of. 2. `view_ticket_incident` permission can view incident tickets from organizations they are not apart of. 3. `view_ticket_request` permission can view request tickets from organizations they are not apart of. 4. `view_ticket_problem` permission can view problem tickets from organizations they are not apart of. The access to view the tickets from different organizations is only applicable when browsing the API endpoints for the tickets in question. The Centurion UI is not affected. Project Tasks, although a "ticket type" are also **Not** affected. This issue has been addressed in release version 1.3.1 and users are advised to upgrade. Users unable to upgrade may remove the ticket view permissions from users which would alleviate this vulnerability, if this is deemed not-viable, Upgrading is recommended.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Defines isolation boundaries by specifying which external systems may access or process organization data.
Maintains isolation and compartmentalization by restricting flows between security domains or levels.
Reviewing the continued need for connections supports isolation and compartmentalization.
Locating systems away from hazards improves isolation and compartmentalization from external physical or environmental threats.
The CONOPS must articulate isolation and compartmentalization expectations for security and privacy, making architectural failures in separation of duties or domains harder to overlook.
Security architectures commonly incorporate isolation and compartmentalization strategies to limit the impact of compromises.
Organization-wide privacy program leadership ensures proper isolation and compartmentalization of personal data.
Oversight ensures data-matching activities maintain required isolation between distinct data sets and authorized user communities.