Vulnerability in aurelia-path (CVE-2021-41097)
Summary
Vulnerability in aurelia-path (CVE-2021-41097). Data can be tampered with by attackers. Exploitable via Object. Mitigation: upgrade to 1.1.7 or later.
Original description
The description as published by the source.
aurelia-path is part of the Aurelia platform and contains utilities for path manipulation. There is a prototype pollution vulnerability in aurelia-path before version 1.1.7. The vulnerability exposes Aurelia application that uses aurelia-path package to parse a string. The majority of this will be Aurelia applications that employ the aurelia-router package. An example is this could allow an attacker to change the prototype of base object class Object by tricking an application to parse the following URL: https://aurelia.io/blog/?__proto__[asdf]=asdf. The problem is patched in version 1.1.7.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-41097 has been found in aurelia-path.
Attackers can target a specific entry point like Object over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade aurelia-path to 1.1.7 or later.
If unsure, ask your IT team or search "aurelia-path CVE-2021-41097" on the vendor's site.
CVE-2021-41097 (aurelia-path) — CWE-1321
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Object
Patched: 1.1.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in aurelia-path. Attackers reach the vulnerable code path via Object without authentication.
Check the vendor advisory for the affected versions of aurelia-path. Attack surface: Object.
Severity: ?. Data can be tampered with by attackers.
Update to 1.1.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'aurelia-path' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'aurelia-path' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
aurelia-pathを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade aurelia-path to 1.1.7ステージング環境で 1.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory npmjs.com
- package github.com
- patch github.com
- report github.com