LiveActive security incident?Get immediate response
CVE Record

CVE-2005-0366: The integrity check feature in OpenPGP, when handling a message that was encrypted using cipher feedback (C...

The integrity check feature in OpenPGP, when handling a message that was encrypted using cipher feedback (CFB) mode, allows remote attackers to recover part of the plaintext via a chosen-ciphertext attack when the first 2 bytes of a message block are known, and an oracle or other mechanism is available to determine whether an integrity check failed.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2005-0366 is a cryptographic weakness in OpenPGP integrity checking for CFB-encrypted messages. Under specific conditions, an attacker may recover part of a protected message. The issue is serious for organizations relying on affected OpenPGP software for sensitive email or file protection, but the source bundle does not show active exploitation or a complete affected-product list. Exposure is most likely where legacy OpenPGP implementations process attacker-supplied encrypted messages and reveal distinguishable integrity-check failure behavior. The bundle names OpenPGP broadly but does not identify specific affected products or versions in the structured affected field. Handle as a targeted legacy cryptography exposure. It is not evidenced as an active mass-exploitation emergency, but organizations depending on OpenPGP for confidential communications should verify affected software and update unsupported components. Mitigation focus: Check current vendor advisories for affected OpenPGP implementations and supported fixes.; Upgrade or replace unsupported OpenPGP software handling sensitive encrypted messages.; Avoid exposing detailed integrity-check failure differences to untrusted senders or callers..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-0366 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.