🛡️ AZL-9891 — curl (CVE-2022-30115)
Description
CVE-2022-30115 affecting package curl for versions less than 7.83.1-1
Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is provided in theURL. This mechanism could be bypassed if the host name in the given URL used atrailing dot while not using one when it built the HSTS cache. Or the otherway around - by having the trailing dot in the HSTS cache and *not* using thetrailing dot in the URL.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.
Affected software
AZL-9891 is recorded against 1 package.
- curl (fixed in 7.83.1-1)
Timeline and source
Published on 2 June 2022 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| curl | — | 7.83.1-1 |
References
Similar Threats
- Unknown ALPINE-CVE-2022-32221
- Unknown ALPINE-CVE-2022-35260
- Unknown ALPINE-CVE-2022-35252
- Unknown ALPINE-CVE-2022-32206
- Unknown ALPINE-CVE-2022-32205
Free Vulnerability Check
Is your site affected by AZL-9891?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-9891 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.