First published: Mon Oct 28 2013(Updated: )
The RPM GPG key import and handling feature in libzypp 12.15.0 and earlier reports a different key fingerprint than the one used to sign a repository when multiple key blobs are used, which might allow remote attackers to trick users into believing that the repository was signed by a more-trustworthy key.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SUSE Libzypp | <=12.15.0 | |
SUSE Libzypp | =11.2 | |
SUSE Libzypp | =11.3 | |
SUSE Libzypp | =11.4 | |
SUSE Libzypp | =12.1 | |
SUSE Libzypp | =12.2 | |
SUSE Libzypp | =12.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-3704 has a medium severity rating, indicating a potential risk for remote attackers.
To fix CVE-2013-3704, upgrade to a version of libzypp that is newer than 12.15.0.
CVE-2013-3704 affects libzypp versions 12.15.0 and earlier, as well as 11.2, 11.3, 11.4, 12.1, 12.2, and 12.3.
CVE-2013-3704 may allow remote attackers to mislead users into trusting a less trustworthy repository.
Yes, CVE-2013-3704 is a documented vulnerability in Novell Libzypp that has been acknowledged by the community.