‼ CVE-2021-27784 ‼
📖 Read
via "National Vulnerability Database".
The provided HCL Launch Container images contain non-unique HTTPS certificates and a database encryption key. The fix provides directions and tools to replace the non-unique keys and certificates. This does not affect the standard installer packages.📖 Read
via "National Vulnerability Database".
📢 Australia's Department of Defence becomes latest victim of regional ransomware attacks 📢
📖 Read
via "ITPro".
Military information was not stolen in the breach, which may affect the records of 40,000 defence personnel📖 Read
via "ITPro".
ITPro
Australia's Department of Defence becomes latest victim of regional ransomware attacks
Military information was not stolen in the breach, which may affect the records of 40,000 defence personnel
👍1
📢 MSPs' next biggest investment will be in MDR and dark web monitoring 📢
📖 Read
via "ITPro".
Research showed that providers were torn on the decisions of what their next big offering will be📖 Read
via "ITPro".
channelpro
MSPs' next biggest investment will be in MDR and dark web monitoring
Research showed that providers were torn on the decisions of what their next big offering will be
‼ CVE-2022-43354 ‼
📖 Read
via "National Vulnerability Database".
Sanitization Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /admin/?page=orders/manage_request.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-2572 ‼
📖 Read
via "National Vulnerability Database".
In affected versions of Octopus Server where access is managed by an external authentication provider, it was possible that the API key/keys of a disabled/deleted user were still valid after the access was revoked.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-3373 ‼
📖 Read
via "National Vulnerability Database".
Out of bounds write in V8 in Google Chrome prior to 106.0.5249.91 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-41552 ‼
📖 Read
via "National Vulnerability Database".
Server-Side Request Forgery (SSRF) vulnerability in Hitachi Infrastructure Analytics Advisor on Linux (Data Center Analytics, Analytics probe components), Hitachi Ops Center Analyzer on Linux (Hitachi Ops Center Analyzer detail view, Hitachi Ops Center Analyzer probe components) allows Server Side Request Forgery.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43353 ‼
📖 Read
via "National Vulnerability Database".
Sanitization Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /admin/?page=orders/view_order.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-41553 ‼
📖 Read
via "National Vulnerability Database".
Insertion of Sensitive Information into Temporary File vulnerability in Hitachi Infrastructure Analytics Advisor on Linux (Analytics probe component), Hitachi Ops Center Analyzer on Linux (Hitachi Ops Center Analyzer probe component) allows local users to gain sensitive information.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-36605 ‼
📖 Read
via "National Vulnerability Database".
Incorrect Default Permissions vulnerability in Hitachi Infrastructure Analytics Advisor on Linux (Analytics probe component), Hitachi Ops Center Analyzer on Linux (Analyzer probe component), Hitachi Ops Center Viewpoint on Linux (Viewpoint RAID Agent component) allows local users to read and write specific files.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-3191 ‼
📖 Read
via "National Vulnerability Database".
Insertion of Sensitive Information into Log File vulnerability in Hitachi Ops Center Analyzer on Linux (Virtual Strage Software Agent component) allows local users to gain sensitive information.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-3370 ‼
📖 Read
via "National Vulnerability Database".
Use after free in Custom Elements in Google Chrome prior to 106.0.5249.91 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-44542 ‼
📖 Read
via "National Vulnerability Database".
lesspipe before 2.06 allows attackers to execute code via Perl Storable (pst) files, because of deserialized object destructor execution via a key/value pair in a hash.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43355 ‼
📖 Read
via "National Vulnerability Database".
Sanitization Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /php-sms/classes/Master.php?f=delete_service.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-42314 ‼
📖 Read
via "National Vulnerability Database".
Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction📖 Read
via "National Vulnerability Database".
‼ CVE-2022-42319 ‼
📖 Read
via "National Vulnerability Database".
Xenstore: Guests can cause Xenstore to not free temporary memory When working on a request of a guest, xenstored might need to allocate quite large amounts of memory temporarily. This memory is freed only after the request has been finished completely. A request is regarded to be finished only after the guest has read the response message of the request from the ring page. Thus a guest not reading the response can cause xenstored to not free the temporary memory. This can result in memory shortages causing Denial of Service (DoS) of xenstored.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-42320 ‼
📖 Read
via "National Vulnerability Database".
Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-42315 ‼
📖 Read
via "National Vulnerability Database".
Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction📖 Read
via "National Vulnerability Database".
‼ CVE-2022-42310 ‼
📖 Read
via "National Vulnerability Database".
Xenstore: Guests can create orphaned Xenstore nodes By creating multiple nodes inside a transaction resulting in an error, a malicious guest can create orphaned nodes in the Xenstore data base, as the cleanup after the error will not remove all nodes already created. When the transaction is committed after this situation, nodes without a valid parent can be made permanent in the data base.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-42317 ‼
📖 Read
via "National Vulnerability Database".
Xenstore: guests can let run xenstored out of memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Malicious guests can cause xenstored to allocate vast amounts of memory, eventually resulting in a Denial of Service (DoS) of xenstored. There are multiple ways how guests can cause large memory allocations in xenstored: - - by issuing new requests to xenstored without reading the responses, causing the responses to be buffered in memory - - by causing large number of watch events to be generated via setting up multiple xenstore watches and then e.g. deleting many xenstore nodes below the watched path - - by creating as many nodes as allowed with the maximum allowed size and path length in as many transactions as possible - - by accessing many nodes inside a transaction📖 Read
via "National Vulnerability Database".
‼ CVE-2022-42321 ‼
📖 Read
via "National Vulnerability Database".
Xenstore: Guests can crash xenstored via exhausting the stack Xenstored is using recursion for some Xenstore operations (e.g. for deleting a sub-tree of Xenstore nodes). With sufficiently deep nesting levels this can result in stack exhaustion on xenstored, leading to a crash of xenstored.📖 Read
via "National Vulnerability Database".