rhsa-2003:390
Vulnerability from csaf_redhat
Published
2003-12-11 00:25
Modified
2024-11-21 22:54
Summary
Red Hat Security Advisory: : Updated gnupg packages disable ElGamal keys
Notes
Topic
Updated gnupg packages are now available for Red Hat Linux. These updates
disable the ability to generate ElGamal keys (used for both signing and
encrypting) and disable the ability to use ElGamal public keys for
encrypting data.
Details
GnuPG is a utility for encrypting data and creating digital signatures.
Phong Nguyen identified a severe bug in the way GnuPG creates and uses
ElGamal keys, when those keys are used both to sign and encrypt data. This
vulnerability can be used to trivially recover the private key. While the
default behavior of GnuPG when generating keys does not lead to the
creation of unsafe keys, by overriding the default settings an unsafe key
could have been created.
If you are using ElGamal keys, you should revoke those keys immediately.
The packages included in this update do not make ElGamal keys safe to use;
they merely include a patch by David Shaw that disables functions that
would generate or use ElGamal keys.
To determine if your key is affected, run the following command to obtain a
list of secret keys that you have on your secret keyring:
gpg --list-secret-keys
The output of this command includes both the size and type of the keys
found, and will look similar to this example:
/home/example/.gnupg/secring.gpg
----------------------------------------------------
sec 1024D/01234567 2000-10-17 Example User <example@example.com>
uid Example User <example@example.com>
The key length, type, and ID are listed together, separated by a forward
slash. In the example output above, the key's type is "D" (DSA, sign
and encrypt). Your key is unsafe if and only if the key type is "G"
(ElGamal, sign and encrypt). In the above example, the secret key is safe
to use, while the secret key in the following example is not:
/home/example/.gnupg/secring.gpg
----------------------------------------------------
sec 1024G/01234567 2000-10-17 Example User <example@example.com>
uid Example User <example@example.com>
For more details regarding this issue, as well as instructions on how to
revoke any keys that are unsafe, refer to the advisory available from the
GnuPG web site:
http://www.gnupg.org/
Terms of Use
This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.
{
"document": {
"aggregate_severity": {
"namespace": "https://access.redhat.com/security/updates/classification/",
"text": "Important"
},
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Copyright \u00a9 Red Hat, Inc. All rights reserved.",
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "Updated gnupg packages are now available for Red Hat Linux. These updates\ndisable the ability to generate ElGamal keys (used for both signing and\nencrypting) and disable the ability to use ElGamal public keys for\nencrypting data.",
"title": "Topic"
},
{
"category": "general",
"text": "GnuPG is a utility for encrypting data and creating digital signatures.\n\nPhong Nguyen identified a severe bug in the way GnuPG creates and uses\nElGamal keys, when those keys are used both to sign and encrypt data. This\nvulnerability can be used to trivially recover the private key. While the\ndefault behavior of GnuPG when generating keys does not lead to the\ncreation of unsafe keys, by overriding the default settings an unsafe key\ncould have been created.\n\nIf you are using ElGamal keys, you should revoke those keys immediately.\n\nThe packages included in this update do not make ElGamal keys safe to use;\nthey merely include a patch by David Shaw that disables functions that\nwould generate or use ElGamal keys.\n\nTo determine if your key is affected, run the following command to obtain a\nlist of secret keys that you have on your secret keyring:\n\ngpg --list-secret-keys\n\nThe output of this command includes both the size and type of the keys\nfound, and will look similar to this example:\n\n/home/example/.gnupg/secring.gpg\n----------------------------------------------------\nsec 1024D/01234567 2000-10-17 Example User \u003cexample@example.com\u003e\nuid Example User \u003cexample@example.com\u003e\n\nThe key length, type, and ID are listed together, separated by a forward\nslash. In the example output above, the key\u0027s type is \"D\" (DSA, sign\nand encrypt). Your key is unsafe if and only if the key type is \"G\"\n(ElGamal, sign and encrypt). In the above example, the secret key is safe\nto use, while the secret key in the following example is not:\n\n/home/example/.gnupg/secring.gpg\n----------------------------------------------------\nsec 1024G/01234567 2000-10-17 Example User \u003cexample@example.com\u003e\nuid Example User \u003cexample@example.com\u003e\n\nFor more details regarding this issue, as well as instructions on how to\nrevoke any keys that are unsafe, refer to the advisory available from the\nGnuPG web site:\n\nhttp://www.gnupg.org/",
"title": "Details"
},
{
"category": "legal_disclaimer",
"text": "This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.",
"title": "Terms of Use"
}
],
"publisher": {
"category": "vendor",
"contact_details": "https://access.redhat.com/security/team/contact/",
"issuing_authority": "Red Hat Product Security is responsible for vulnerability handling across all Red Hat products and services.",
"name": "Red Hat Product Security",
"namespace": "https://www.redhat.com"
},
"references": [
{
"category": "self",
"summary": "https://access.redhat.com/errata/RHSA-2003:390",
"url": "https://access.redhat.com/errata/RHSA-2003:390"
},
{
"category": "external",
"summary": "http://lists.gnupg.org/pipermail/gnupg-announce/2003q4/000276.html",
"url": "http://lists.gnupg.org/pipermail/gnupg-announce/2003q4/000276.html"
},
{
"category": "external",
"summary": "http://lists.gnupg.org/pipermail/gnupg-users/2003-November/020779.html",
"url": "http://lists.gnupg.org/pipermail/gnupg-users/2003-November/020779.html"
},
{
"category": "external",
"summary": "http://lists.gnupg.org/pipermail/gnupg-announce/2003q4/000277.html",
"url": "http://lists.gnupg.org/pipermail/gnupg-announce/2003q4/000277.html"
},
{
"category": "self",
"summary": "Canonical URL",
"url": "https://security.access.redhat.com/data/csaf/v2/advisories/2003/rhsa-2003_390.json"
}
],
"title": "Red Hat Security Advisory: : Updated gnupg packages disable ElGamal keys",
"tracking": {
"current_release_date": "2024-11-21T22:54:04+00:00",
"generator": {
"date": "2024-11-21T22:54:04+00:00",
"engine": {
"name": "Red Hat SDEngine",
"version": "4.2.1"
}
},
"id": "RHSA-2003:390",
"initial_release_date": "2003-12-11T00:25:00+00:00",
"revision_history": [
{
"date": "2003-12-11T00:25:00+00:00",
"number": "1",
"summary": "Initial version"
},
{
"date": "2003-12-10T00:00:00+00:00",
"number": "2",
"summary": "Last updated version"
},
{
"date": "2024-11-21T22:54:04+00:00",
"number": "3",
"summary": "Last generated version"
}
],
"status": "final",
"version": "3"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_name",
"name": "Red Hat Linux 7.1",
"product": {
"name": "Red Hat Linux 7.1",
"product_id": "Red Hat Linux 7.1",
"product_identification_helper": {
"cpe": "cpe:/o:redhat:linux:7.1"
}
}
},
{
"category": "product_name",
"name": "Red Hat Linux 7.2",
"product": {
"name": "Red Hat Linux 7.2",
"product_id": "Red Hat Linux 7.2",
"product_identification_helper": {
"cpe": "cpe:/o:redhat:linux:7.2"
}
}
},
{
"category": "product_name",
"name": "Red Hat Linux 7.3",
"product": {
"name": "Red Hat Linux 7.3",
"product_id": "Red Hat Linux 7.3",
"product_identification_helper": {
"cpe": "cpe:/o:redhat:linux:7.3"
}
}
},
{
"category": "product_name",
"name": "Red Hat Linux 8.0",
"product": {
"name": "Red Hat Linux 8.0",
"product_id": "Red Hat Linux 8.0",
"product_identification_helper": {
"cpe": "cpe:/o:redhat:linux:8.0"
}
}
},
{
"category": "product_name",
"name": "Red Hat Linux 9",
"product": {
"name": "Red Hat Linux 9",
"product_id": "Red Hat Linux 9",
"product_identification_helper": {
"cpe": "cpe:/o:redhat:linux:9"
}
}
}
],
"category": "product_family",
"name": "Red Hat Linux"
}
],
"category": "vendor",
"name": "Red Hat"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2003-0971",
"ids": [
{
"system_name": "Red Hat Bugzilla ID",
"text": "1617110"
}
],
"notes": [
{
"category": "description",
"text": "GnuPG (GPG) 1.0.2, and other versions up to 1.2.3, creates ElGamal type 20 (sign+encrypt) keys using the same key component for encryption as for signing, which allows attackers to determine the private key from a signature.",
"title": "Vulnerability description"
},
{
"category": "summary",
"text": "security flaw",
"title": "Vulnerability summary"
}
],
"product_status": {
"fixed": [
"Red Hat Linux 7.1",
"Red Hat Linux 7.2",
"Red Hat Linux 7.3",
"Red Hat Linux 8.0",
"Red Hat Linux 9"
]
},
"references": [
{
"category": "self",
"summary": "Canonical URL",
"url": "https://access.redhat.com/security/cve/CVE-2003-0971"
},
{
"category": "external",
"summary": "RHBZ#1617110",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1617110"
},
{
"category": "external",
"summary": "https://www.cve.org/CVERecord?id=CVE-2003-0971",
"url": "https://www.cve.org/CVERecord?id=CVE-2003-0971"
},
{
"category": "external",
"summary": "https://nvd.nist.gov/vuln/detail/CVE-2003-0971",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2003-0971"
}
],
"release_date": "2003-11-27T00:00:00+00:00",
"remediations": [
{
"category": "vendor_fix",
"date": "2003-12-11T00:25:00+00:00",
"details": "Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nTo update all RPMs for your particular architecture, run:\n\nrpm -Fvh [filenames]\n\nwhere [filenames] is a list of the RPMs you wish to upgrade. Only those\nRPMs which are currently installed will be updated. Those RPMs which are\nnot installed but included in the list will not be updated. Note that you\ncan also use wildcards (*.rpm) if your current directory *only* contains\nthe desired RPMs.\n\nPlease note that this update is also available via Red Hat Network. Many\npeople find this an easier way to apply updates. To use Red Hat Network,\nlaunch the Red Hat Update Agent with the following command:\n\nup2date\n\nThis will start an interactive process that will result in the appropriate\nRPMs being upgraded on your system.\n\nIf up2date fails to connect to Red Hat Network due to SSL Certificate \nErrors, you need to install a version of the up2date client with an updated \ncertificate. The latest version of up2date is available from the Red Hat \nFTP site and may also be downloaded directly from the RHN website:\n\nhttps://rhn.redhat.com/help/latest-up2date.pxt",
"product_ids": [
"Red Hat Linux 7.1",
"Red Hat Linux 7.2",
"Red Hat Linux 7.3",
"Red Hat Linux 8.0",
"Red Hat Linux 9"
],
"restart_required": {
"category": "none"
},
"url": "https://access.redhat.com/errata/RHSA-2003:390"
}
],
"threats": [
{
"category": "impact",
"details": "Important"
}
],
"title": "security flaw"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…