LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38189: An issue was discovered in the lettre crate before 0.9.6 for Rust.

An issue was discovered in the lettre crate before 0.9.6 for Rust. In an e-mail message body, an attacker can place a . character after two <CR><LF> sequences and then inject arbitrary SMTP commands.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-38189 affects Rust applications using the lettre email crate before 0.9.6. If an attacker controls part of an email body, they may be able to break out of the message content and inject SMTP commands. Exposure depends on whether the application sends attacker-supplied email bodies through vulnerable lettre versions.

Executive priority

Treat this as a targeted dependency remediation item, not an emergency without exposure evidence. Prioritize systems that send externally influenced email content, customer messages, invitations, forms, or support notifications.

Technical view

The issue is SMTP command injection in lettre before 0.9.6. The CVE states that a message body containing a dot after two CRLF sequences can allow arbitrary SMTP command injection. No CVSS, CWE, affected CPEs, or public exploitation evidence are provided in the bundle.

Likely exposure

Most exposure is in Rust services that use lettre before 0.9.6 to send email where message bodies include untrusted user input. Internal-only notification systems with fixed templates are less likely exposed, but dependency inventory is required.

Exploitation context

The bundle does not show KEV listing or active exploitation. The described attack requires influence over an email body processed by vulnerable lettre and an SMTP delivery path that interprets injected commands.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, or exploit-status detail is included. The key research task is confirming reachable attacker-controlled message body paths in applications using vulnerable lettre versions.

Mitigation direction

  • Upgrade lettre to version 0.9.6 or later where applicable.
  • Identify services that send user-controlled email content through lettre.
  • Constrain or sanitize untrusted input used in email bodies.
  • Review RustSec advisory guidance before making production changes.

Validation and detection

  • Check Rust dependency manifests and lockfiles for lettre versions before 0.9.6.
  • Map vulnerable dependencies to applications that send outbound email.
  • Review whether email body content can be supplied by external users.
  • Inspect mail logs for unexpected SMTP behavior around affected services.
Prepared
Confidence
medium
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.

cve · low confidence lookup

CVE-2021-38189 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
3Source links

CVSS and timeline data

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

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.