@asymmetric-effort/specifyjs: `data:` URI allowed without size restriction
## Finding **Location**: `core/src/shared/secure-fetch.ts:33-35` `data:` URIs were allowed without any restriction. While `data:` URIs don't make network requests, they can be used for memory exhaustion via very large data URIs. ## Status **Fixed in v0.2.136** — `data:` URIs are now limited to 1MB. URIs exceeding this limit throw an error.
AI Analysis
Technical Summary
The vulnerability in @asymmetric-effort/specifyjs involved unrestricted acceptance of data: URIs in the code at core/src/shared/secure-fetch.ts lines 33-35. Although data: URIs do not trigger network requests, their unrestricted size could be exploited to cause memory exhaustion. The issue was addressed in version 0.2.136 by enforcing a 1MB size limit on data: URIs, rejecting any that exceed this threshold.
Potential Impact
Unrestricted data: URIs could be used to cause memory exhaustion in applications using affected versions of @asymmetric-effort/specifyjs prior to 0.2.136. This may lead to denial of service due to resource exhaustion. No network-based attack or privilege escalation is indicated.
Mitigation Recommendations
Upgrade to @asymmetric-effort/specifyjs version 0.2.136 or later, where data: URIs are limited to 1MB and larger URIs throw an error. This official fix effectively mitigates the vulnerability.
@asymmetric-effort/specifyjs: `data:` URI allowed without size restriction
Description
## Finding **Location**: `core/src/shared/secure-fetch.ts:33-35` `data:` URIs were allowed without any restriction. While `data:` URIs don't make network requests, they can be used for memory exhaustion via very large data URIs. ## Status **Fixed in v0.2.136** — `data:` URIs are now limited to 1MB. URIs exceeding this limit throw an error.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in @asymmetric-effort/specifyjs involved unrestricted acceptance of data: URIs in the code at core/src/shared/secure-fetch.ts lines 33-35. Although data: URIs do not trigger network requests, their unrestricted size could be exploited to cause memory exhaustion. The issue was addressed in version 0.2.136 by enforcing a 1MB size limit on data: URIs, rejecting any that exceed this threshold.
Potential Impact
Unrestricted data: URIs could be used to cause memory exhaustion in applications using affected versions of @asymmetric-effort/specifyjs prior to 0.2.136. This may lead to denial of service due to resource exhaustion. No network-based attack or privilege escalation is indicated.
Mitigation Recommendations
Upgrade to @asymmetric-effort/specifyjs version 0.2.136 or later, where data: URIs are limited to 1MB and larger URIs throw an error. This official fix effectively mitigates the vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2944-57xv-2682
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a46ecbb27e9c7971943cdfc
Added to database: 07/02/2026, 22:56:59 UTC
Last enriched: 07/02/2026, 23:14:38 UTC
Last updated: 07/31/2026, 13:34:15 UTC
Views: 32
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.