🛡️ CVE-2020-29050 on Debian — sphinxsearch
Description
SphinxSearch in Sphinx Technologies Sphinx through 3.1.1 allows directory traversal (in conjunction with CVE-2019-14511) because the mysql client can be used for CALL SNIPPETS and load_file operations on a full pathname (e.g., a file in the /etc directory). NOTE: this is unrelated to CMUSphinx.
Distribution advisory
This page covers CVE-2020-29050 as tracked by Debian, for the package sphinxsearch. The fix is available in version 2.2.11-3; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.
Affected software
DEBIAN-CVE-2020-29050 is recorded against 1 package.
- sphinxsearch (fixed in 2.2.11-3)
Timeline and source
Published on 10 January 2022 and last revised on 15 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2020-29050 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| sphinxsearch | — | 2.2.11-3 |
References
Similar Threats
- Unknown DLA-2882-1
- Unknown UBUNTU-CVE-2020-29050
- Unknown DSA-5036-1
Free Vulnerability Check
Is your site affected by DEBIAN-CVE-2020-29050?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against DEBIAN-CVE-2020-29050 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.