This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
Search vulnerabilities
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
Nokia BMC Root Privilege OS Command Injection via Log Scanner Input
Nokia Broadcast Message Center (BMC) before 13.1 allows an unauthenticated remote attacker to do OS command injection as root via shell metacharacters in the Log Scanner Search Pattern field.
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
mm/memory_hotplug: fix memory block reference leak on remove
In the Linux kernel, the following vulnerability has been resolved: mm/memory_hotplug: fix memory block reference leak on remove Patch series "mm: Fix memory block leaks and locking", v2. This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter. This patch (of 2): remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device. That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem->altmap and clearing mem->altmap, before removing the memory block device.
Hard-coded / Backdoor Accounts
Two undocumented privileged accounts exist in Autel Maxi Charger Single firmware through V1.03.51. The accounts use vendor-defined password derivation mechanisms based on device-specific values, allowing an attacker with knowledge of the algorithm and required inputs to authenticate to the web management interface with administrative privileges.
Backdoor Authentication Token
Autel Maxi Charger Single firmware through V1.03.51 contains a hard-coded authentication token that bypasses authorization checks for multiple management endpoints. An attacker can supply the special token value to invoke privileged functionality without valid authentication.
Metabase SQL injection via password reset endpoint
Metabase allows a remote, unauthenticated attacker to inject arbitrary SQL via the '/reset_password' database endpoint and gain administrator access to the connected Metabase instance.
Microsoft SharePoint Server Spoofing Vulnerability
Deserialization of untrusted data in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.
Visual Studio Code Security Feature Bypass Vulnerability
Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.
Visual Studio Code Information Disclosure Vulnerability
Improper neutralization of special elements used in a command ('command injection') in Visual Studio Code allows an unauthorized attacker to disclose information over a network.
Easy Accordion <= 3.1.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'accordionTitleTag' Block Attribute
The Easy Accordion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'accordionTitleTag' block attribute in versions up to, and including, 3.1.8. This is due to insufficient input sanitization and output escaping in the accordion_header_renderer() function, which emits the attacker-supplied tag name using esc_attr() in an HTML tag-name context instead of tag_escape(). This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.