Security readout for executives and security teams
Plain-English summary
OTRS can export private and public PGP or S/MIME keys using the same filename. A privileged user may accidentally send a private key when intending to share a public key. The business risk is confidentiality loss of email encryption or signing material, not direct system takeover.
Executive priority
Treat as a moderate-priority confidentiality issue. Prioritize remediation for OTRS systems that process sensitive email, use encryption or signing, or allow multiple administrators to export keys.
Technical view
CVE-2020-1774 is a CWE-201 information disclosure issue affecting OTRS Community Edition 5.0.42 and earlier, 6.0.27 and earlier, and OTRS 7.0.16 and earlier. CVSS 3.1 is 4.5, with network attack vector, high privileges required, user interaction required, and high confidentiality impact.
Likely exposure
Exposure is limited to organizations running affected OTRS versions and using PGP or S/MIME key or certificate export. The vulnerable action requires a privileged user and a mistake during key sharing.
Exploitation context
The provided sources do not show active exploitation, and this CVE is not listed as KEV. The risk is accidental disclosure or social misuse of confusing export filenames rather than a simple unauthenticated exploit path.
Researcher notes
Evidence is specific but narrow: the sources describe filename confusion during key or certificate export. They do not provide exploit prevalence, active exploitation, or detailed fixed version information in the supplied bundle.
Mitigation direction
- Identify whether affected OTRS or otrs2 versions are deployed.
- Apply the OTRS advisory guidance or Debian security update where applicable.
- Restrict key and certificate export permissions to trusted administrators.
- Warn users not to share exported files until private/public status is verified.
- Rotate any private key that may have been sent externally.
Validation and detection
- Inventory OTRS versions against the affected version ranges.
- Check Debian package status if using distro-managed otrs2 packages.
- Review who can download PGP or S/MIME keys and certificates.
- Confirm export handling clearly distinguishes private and public key files.
- Investigate historical incidents where exported keys were shared externally.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-201: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-1774 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N0.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://otrs.com/release-notes/otrs-security-advisory-2020-11/CVE reference
- [debian-lts-announce] 20200501 [SECURITY] [DLA 2198-1] otrs2 security updateCVE reference · mailing-list
- [debian-lts-announce] 20230831 [SECURITY] [DLA 3551-1] otrs2 security updateCVE reference · mailing-list
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information Into Sent Data
Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.