Vulnerability in uap-core (CVE-2020-5243)
Summary
Vulnerability in uap-core (CVE-2020-5243). Risk of unauthorized operations or information disclosure. Exploitable via User-Agent header. Mitigation: upgrade to 0.7.3 or later.
Original description
The description as published by the source.
Impact
Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.
Patches
Please update uap-core to >= v0.7.3
Downstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes.
Details
Each vulnerable regular expression reported here contains 3 overlapping capture groups. Backtracking has approximately cubic time complexity with respect to the length of the user-agent string.
Regex 1:
\bSmartWatch *\( *([^;]+) *; *([^;]+) *;
is vulnerable in portion *([^;]+) * and can be attacked with
"SmartWatch(" + (" " * 3500) + "z"
e.g.
SmartWatch( z
Regex 2:
; *([^;/]+) Build[/ ]Huawei(MT1-U06|[A-Z]+\d+[^\);]+)[^\);]*\)
is vulnerable in portion \d+[^\);]+[^\);]* and can be attacked with
";A Build HuaweiA" + ("4" * 3500) + "z"
Regex 3:
(HbbTV)/[0-9]+\.[0-9]+\.[0-9]+ \([^;]*; *(LG)E *; *([^;]*) *;[^;]*;[^;]*;\)
is vulnerable in portion *([^;]*) * and can be attacked with
"HbbTV/0.0.0 (;LGE;" + ("…
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-2020-5243 has been found in uap-core.
Attackers can target a specific entry point like User-Agent header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade uap-core to 0.7.3 or later.
If unsure, ask your IT team or search "uap-core CVE-2020-5243" on the vendor's site.
CVE-2020-5243 (uap-core) — CWE-1333
Attack vector: remote (network-reachable)
Attack surface: User-Agent header
Patched: 0.7.3 — 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-1333) exists in uap-core. Attackers reach the vulnerable code path via User-Agent header.
Check the vendor advisory for the affected versions of uap-core. Attack surface: User-Agent header.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.7.3.
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 'uap-core' . 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 'uap-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
uap-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade uap-core to 0.7.3ステージング環境で 0.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2020-5243 uap-core Fixed in: 1:0.8.0-1
- Ubuntu UBUNTU-CVE-2020-5243 uap-core
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com