Search: http://45.32.13.180
3 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d260e32207d8cb161b0a72f1337a42c9755b9550a8eda1e70f0b4182273d476b) build/index.js (the package main) appends a hidden eval(atob('...')) block after the legitimate __exportStar boilerplate, separated by a long run of tab characters to push it off-screen in editors. On every require/import of the package, the decoded payload queries an Ethereum RPC/Blockscout endpoint for the latest transaction of the hardcoded EOA 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, interprets the 20-byte tx.to address as two encoded IPv4 addresses, and issues HTTP requests to http://<resolved-ip>:443/0x/cls and http://<resolved-ip>:443/0x/ls. The response carries a payload in the x-payload-b64 header that is XOR-decoded and then executed via spawn('node', ['-e', <decoded>], {detached: true, stdio: 'ignore', windowsHide: true}).unref(), launching a detached hidden Node process on the installer's machine. Module identifiers such as 'http', 'https', 'child_process', and 'spawn' are unicode-escaped (\u00XX) to further hide the behavior. The combination of on-chain C2 resolution (resistant to DNS/domain takedown), multi-layer obfuscation, and hidden detached process execution on import is a remote-code-execution supply-chain attack against any project that installs this version. ## Source: ghsa-malware (037f3ed4ca92b64733adaadc02c839d4fc180a4547c0a191cefb45a57e8833d5) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Medium | 5.3 | EPSS 0.4% | CVE-2026-8723ljharb qs · NULL Pointer Dereference Medium5.3EPSS 0.4%CVE Database V5CVE-2026-8723 ### Summary `qs.stringify` throws `TypeError` when called with `arrayFormat: 'comma'` and `encodeValuesOnly: true` on an array containing `null` or `undefined`. The throw is synchronous and not handled by any of qs's null-related options (`skipNulls`, `strictNullHandling`). ### Details In the comma + `encodeValuesOnly` branch, `lib/stringify.js:145` mapped the array through the raw encoder before joining: ```js obj = utils.maybeMap(obj, encoder); ``` `utils.encode` (`lib/utils.js:195`) reads `str.length` with no null guard, so a `null` or `undefined` element throws `TypeError`. `skipNulls` and `strictNullHandling` are both checked in the per-element loop below this line and never get a chance to run. Same class of bug as the filter-array path fixed in 0c180a4. The vulnerable shape of the comma + `encodeValuesOnly` branch was introduced in 4c4b23d ("encode comma values more consistently", PR #463, 2023-01-19), first released in v6.11.1. #### PoC ```js const qs = require('qs'); qs.stringify({ a: [null, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [undefined, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [null] }, { arrayFormat: 'comma', encodeValuesOnly: true }); // TypeError: Cannot read properties of null (reading 'length') // at encode (lib/utils.js:195:13) // at Object.maybeMap (lib/utils.js:322:37) // at stringify (lib/stringify.js:145:25) ``` #### Fix `lib/stringify.js:145`, applied in 21f80b3 on `main` and released as v6.15.2: ```diff - obj = utils.maybeMap(obj, encoder); + obj = utils.maybeMap(obj, function (v) { + return v == null ? v : encoder(v); + }); ``` `null` and `undefined` now pass through `maybeMap` unchanged and reach the `join(',')` step as-is. For `{ a: [null, 'b'] }` this produces `a=,b`, matching the non-`encodeValuesOnly` comma path (which already joins before encoding and produces `a=%2Cb` for the same input). Single-element `[null]` arrays still collapse via the existing `obj.join(',') || null` and remain subject to `skipNulls` / `strictNullHandling` in the main loop. ### Affected versions `>=6.11.1 <6.15.2` — fixed in v6.15.2. The vulnerable code shape was introduced in 4c4b23d and first shipped in v6.11.1. Earlier versions — including all of 6.7.x, 6.8.x, 6.9.x, 6.10.x, and 6.11.0 — implemented the comma + `encodeValuesOnly` path differently (joining before encoding) and are not affected. Empirically verified across released versions. ### Impact Application code that calls `qs.stringify` with both `arrayFormat: 'comma'` and `encodeValuesOnly: true` (both non-default) on input that may contain a `null` or `undefined` array element will throw synchronously instead of producing a query string. In a typical Node.js HTTP framework (Express, Fastify, Koa, hapi) the sync throw is caught by the framework's error boundary and the affected request returns a 500; the worker process does not exit and subsequent requests are unaffected. The "kills the worker process" framing applies only to call sites outside a request-handler error boundary (background jobs, startup paths, stream pipelines) or to deployments with framework error handling explicitly disabled. The vulnerable input is a `null` or `undefined` entry inside an array; this is reachable from JSON request bodies or from application code constructing arrays from user input, but not from standard HTML form submissions (which produce strings or omitted fields, not literal `null`). | CVE Database V5 | ||
| High | 8.2 | EPSS 0.3% | CVE-2025-4565Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update High8.2EPSS 0.3%GCVE DatabaseCVE-2025-4565 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * automation-controller: AIOHTTP HTTP Request/Response Smuggling (CVE-2025-53643) * automation-controller: AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb (CVE-2025-69223) * automation-controller: Django: Algorithmic complexity in XML Deserializer leads to denial of service (CVE-2025-64460) * automation-controller: urllib3 Streaming API improperly handles highly compressed data (CVE-2025-66471) * python3.11-django: Algorithmic complexity in XML Deserializer leads to denial of service (CVE-2025-64460) * python3.11-protobuf: Unbounded recursion in Python Protobuf (CVE-2025-4565) * python3.11-urllib3: urllib3 Streaming API improperly handles highly compressed data (CVE-2025-66471) * receptor: Excessive resource consumption when printing error string for host certificate validation in crypto/x509 (CVE-2025-61729) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation Platform * Reduced cognitive complexity in _sync_user_superuser_flag (AAP-62771) * The FEATURE_GATEWAY_IPV6_USAGE_ENABLED feature flag has been removed and IPv6 support is enabled by default (AAP-61805) * Fixed an issue preventing gateway from working in a pure IPv4 single stack environment when IPv6 is enabled (AAP-60478) * Added dedicated aap.auth_audit logger with specialized formatters and handlers (AAP-60364) * Introduced new logs for authentication events (AAP-60364) * automation-gateway has been updated to 2.6.20260121 * python3.11-django-ansible-base has been updated to 2.6.20260121 Automation Platform UI * Page titles now reflect the current page content (AAP-61754) * Allow full search in resource dropdowns (AAP-57712) * Fixed an issue that occasionally showed a bad request status when navigating between different pages (AAP-56701) * Fixed filtering by name in Collections page (AAP-56529) * Fixed clear/browse button behavior in Client Certificate and Client Key (AAP-55296) * Fixed an issue where a Rulebook Activation in workers offline status could not be disabled or deleted (AAP-52714) * Fixed an issue where workflow job templates node credentials are missing after save for job template nodes that have a default credential that is promptable (AAP-52638) * Fixed an issue where the gateway UI reset the order of an auth mapping when the entity was edited by the user (AAP-52258) * Improves labels and descriptions for Authenticator Mappings details (AAP-51295) * Resolved an issue where controller unavailability rendered the entire AAP UI inaccessible (AAP-50106) * Fixed descriptions for Remotes and Remote Registries (AAP-49838) * Survey textarea "Default Answer" field now properly accepts newlines when pressing Enter (AAP-49820) * Fixed review page on Workflow Approval Nodes (AAP-49433) * Fixed editing of "Days of data to keep" value in management job schedules (AAP-48972) * Editing and saving credentials that use external credential lookup plugins (such as CyberArk) no longer fails with an error message (AAP-44813) * Fixed an issue where the SAML Service Provider extra configuration data field could not be cleared in the UI, as it would automatically reset to the default value (AAP-43661) * Resolved an issue where ad-hoc commands failed with a "Bad Request" error when using credentials configured with "Prompt on launch" for password fields (AAP-43603) * Updated modal warning message and layout when enabling a copied Rulebook Activation (AAP-42574) * automation-platform-ui has been updated to 2.6.5 Automation controller * Added runtime feature flags (AAP-62686) * automation-controller has been updated to 4.7.8 * receptor has been updated to 1.6.3 Automation hub * Autocomplete attribute added to the Automation Hub API password field (AAP-59910) * automation-hub has been updated to 4.11.5 * python3.11-galaxy-importer has been updated to 0.4.37 * python3.11-galaxy-ng has been updated to 4.11.5 * python3.11-pulpcore has been updated to 3.49.49 Event-Driven Ansible * Added x-ai-description field to the activation PATCH method (AAP-61969) * automation-eda-controller has been updated to 1.2.4 Container-based Ansible Automation Platform * Added lTLS support to lightspeed chatbot service (AAP-60900) * system-prompt was optimized for granite and openai models (AAP-60898) * Added ipv6 support (AAP-60532) * Fixed an issue w | GCVE Database |
Page 1 of 1