https://feed.craftedsignal.io/vendors/asymmetric-effort/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 03 Jul 2026 11:47:22 +0000https://feed.craftedsignal.io/briefs/2026-07-specifyjs-url-parse-failure/Fri, 03 Jul 2026 11:47:22 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-specifyjs-url-parse-failure/A high-severity vulnerability, CVE-2026-50288, in the `@asymmetric-effort/specifyjs` npm package (versions prior to 0.2.136) allows for the silent bypass of HTTPS validation by mishandling URL parse errors in the `assertSecureUrl` function, which can lead to Server-Side Request Forgery (SSRF).A critical vulnerability, tracked as CVE-2026-50288, has been identified in the @asymmetric-effort/specifyjs npm package, specifically affecting versions prior to 0.2.136. This flaw resides within the assertSecureUrl function, intended to enforce HTTPS validation for URLs. The vulnerability occurs because the function's catch block for new URL() parse errors silently returns without re-throwing the error, effectively bypassing security checks. This oversight allows requests for malformed URLs to proceed without proper HTTPS validation, potentially enabling Server-Side Request Forgery (SSRF) attacks. Defenders should be aware that applications utilizing vulnerable versions of this library are susceptible to requests being directed to unintended or malicious destinations, jeopardizing internal network security and data integrity.

Attack Chain

1. An attacker identifies an application that uses the @asymmetric-effort/specifyjs library, specifically a vulnerable version (prior to 0.2.136).
2. The attacker crafts a specially malformed URL that will cause new URL() to throw a parse error when processed by the assertSecureUrl function.
3. The attacker sends this crafted URL to the vulnerable application, likely through a user-controlled input field that expects a URL.
4. The application processes the input URL using the assertSecureUrl function for security validation.
5. During validation, new URL() throws an error due to the malformed input provided by the attacker.
6. Instead of re-throwing the error or blocking the request, the assertSecureUrl function's catch block silently returns, indicating success despite the parse failure and lack of HTTPS validation.
7. The application proceeds to make a request to the unvalidated, and potentially attacker-controlled, internal or external endpoint.
8. This successful bypass enables Server-Side Request Forgery (SSRF), allowing the attacker to access or manipulate internal resources, conduct port scanning, or exfiltrate sensitive data.

Impact

The primary impact of CVE-2026-50288 is the potential for Server-Side Request Forgery (SSRF) within applications using vulnerable versions of the @asymmetric-effort/specifyjs library. Successful exploitation can allow attackers to force the compromised application server to make requests to internal services, retrieve sensitive data from internal systems (e.g., cloud metadata APIs, internal web services), bypass firewalls, or conduct port scanning of the internal network. Depending on the application's privileges and network access, this can lead to data exfiltration, further compromise of internal systems, or unauthorized actions against other resources, significantly impacting the confidentiality and integrity of the organization's data.

Recommendation

• Prioritize patching CVE-2026-50288 by upgrading @asymmetric-effort/specifyjs to version 0.2.136 or higher immediately. Refer to the GitHub Advisory Database reference for CVE-2026-50288.
• Review your application's dependency tree to identify any instances of @asymmetric-effort/specifyjs at versions earlier than 0.2.136 and ensure all affected packages are updated.

]]>highadvisorynpmsupply-chainvulnerabilityssrfjavascripthttps://feed.craftedsignal.io/briefs/2026-07-nogginlessdom-path-traversal/Fri, 03 Jul 2026 11:29:03 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-nogginlessdom-path-traversal/A path traversal vulnerability (GHSA-322x-v876-g883) in the `matchFileSnapshot` function of the `@asymmetric-effort/nogginlessdom` library allows an attacker to write arbitrary content to any filesystem path with write access when snapshot update mode is active, potentially leading to supply chain compromise in CI/CD environments.A critical path traversal vulnerability, tracked as GHSA-322x-v876-g883, has been identified in the matchFileSnapshot function within the @asymmetric-effort/nogginlessdom JavaScript library, specifically in versions 0.0.21 and earlier. This flaw arises from insufficient validation of the filePath parameter when the library operates in snapshot update mode (e.g., UPDATE_SNAPSHOTS=1 environment variable or setUpdateMode('all')). An attacker capable of controlling the filePath input during testing can exploit this to write arbitrary content to any location on the filesystem where the process has write permissions. This includes creating new directories and overwriting existing files, posing a significant risk, particularly in CI/CD pipelines where untrusted test inputs from pull requests could lead to supply chain compromise.

Attack Chain

1. An attacker crafts malicious test input that includes a specially constructed filePath parameter containing path traversal sequences (e.g., ../../../tmp/evil.txt).
2. The malicious test input is processed in an environment where the @asymmetric-effort/nogginlessdom library is used, and the snapshot update mode is active (UPDATE_SNAPSHOTS=1 or setUpdateMode('all')).
3. The vulnerable matchFileSnapshot function is called with the attacker-controlled filePath and arbitrary content.
4. The fs.existsSync(filePath) check fails because the path is outside the expected directory, triggering the creation logic.
5. The library’s fs.mkdirSync(dir, { recursive: true }); function creates intermediate directories specified by the attacker in the malicious filePath.
6. The fs.writeFileSync(filePath, serialized, 'utf-8'); function writes attacker-controlled serialized content to the arbitrary filePath.
7. In a CI/CD environment, this allows overwriting critical configuration files (e.g., /home/runner/.github/workflows/backdoor.yml), injecting malicious code into build artifacts, or modifying pipeline definitions.
8. The successful write leads to arbitrary code execution, persistence within the build system, or compromise of distributed software.

Impact

The vulnerability allows an attacker to perform arbitrary file writes, creating new directories and overwriting existing files with attacker-controlled content. In CI/CD environments, this is particularly severe as untrusted pull requests could trigger the exploit. Consequences include the complete compromise of build processes, such as overwriting CI configuration files to inject malicious steps, injecting malicious code directly into build artifacts, or modifying source code used in subsequent builds. This directly enables supply chain attacks, potentially affecting all downstream consumers of the compromised software. The specific number of victims is not available, but any organization using vulnerable versions of the library in their CI/CD systems is at risk.

Recommendation

• Upgrade @asymmetric-effort/nogginlessdom to version 0.0.22 or later immediately to apply the patch referenced in GHSA-322x-v876-g883.
• Implement controls to prevent untrusted input from reaching build environments, especially in CI/CD pipelines.
• Review CI/CD pipeline definitions and build artifacts for unauthorized modifications after applying the patch.

]]>highadvisorypath-traversalsupply-chainci/cdnpmvulnerability