LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21440: Support Bundle includes S/Mime and PGP keys

Generated Support Bundles contains private S/MIME and PGP keys if containing folder is not hidden. This issue affects: OTRS AG ((OTRS)) Community Edition 6.0.x version 6.0.1 and later versions. OTRS AG OTRS 7.0.x version 7.0.27 and prior versions; 8.0.x version 8.0.14 and prior versions.

MediumCVSS 5.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some OTRS support bundles could accidentally include private S/MIME or PGP keys. If those bundles were shared with support staff or other third parties, encrypted mail or signed-message trust could be exposed. The issue needs attention where OTRS handles sensitive communications, but exploitation requires privileged access and user interaction.

Executive priority

Prioritize remediation if OTRS processes confidential customer or internal mail, or if support bundles were shared externally. This is not presented as internet-scale active exploitation, but accidental private-key disclosure can create lasting confidentiality and trust risk.

Technical view

CVE-2021-21440 is a CWE-200 information disclosure issue in OTRS support bundle generation. If the key-containing folder is not hidden, generated bundles may contain private S/MIME and PGP keys. The CVSS 3.1 score is 5.2 with high confidentiality impact, low integrity impact, high privileges required, and user interaction required.

Likely exposure

Exposure is most likely in affected OTRS Community Edition 6.0.x from 6.0.1, OTRS 7.0.x through 7.0.27, and OTRS 8.0.x through 8.0.14 where support bundles were generated and shared.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. Practical risk depends on whether an authorized user generated a support bundle and whether that bundle left trusted control while containing private mail keys.

Researcher notes

Evidence is limited to the CVE description, OTRS advisory reference, and Debian LTS update notice. The key exposure condition is folder visibility during support bundle generation. Do not assume broader products, exploit availability, or a specific fixed version beyond the cited affected ranges.

Mitigation direction

  • Apply the vendor security update or current vendor-supported OTRS release.
  • For Debian otrs2 deployments, review and apply DLA 3551-1 or successor packages.
  • Review vendor guidance before generating or sharing support bundles.
  • Rotate S/MIME or PGP private keys found in previously shared bundles.
  • Treat exposed historical support bundles as sensitive secrets.

Validation and detection

  • Inventory OTRS and otrs2 versions against the affected ranges.
  • Identify systems where S/MIME or PGP keys are configured in OTRS.
  • Review historical support bundle generation and sharing records.
  • Check existing support bundles for unintended private key material.
  • Confirm remediation with vendor advisory or Debian package status.
Prepared
Confidence
high
Sources
4

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.

cwe · medium confidence lookup

CWE-200: 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 lookup
cve · low confidence lookup

CVE-2021-21440 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
Medium
CVSS
5.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.2CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N0.94.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.2Medium
CVSS 3.1 vector shape for CVE-2021-21440Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OTRS AG((OTRS)) Community Edition6.0.1Listed
OTRS AGOTRS7.0.x, 8.0.xListed
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.