Skip to content

fix: the oauthbearersmtp in OAuthBearerSMTP.pm - #65

Open
anupamme wants to merge 1 commit into
jmapio:masterfrom
anupamme:fix-repo-jmap-perl-oauthbearer-smtp-tls-enforcement
Open

anupamme wants to merge 1 commit into
jmapio:masterfrom
anupamme:fix-repo-jmap-perl-oauthbearer-smtp-tls-enforcement

Conversation

@anupamme

@anupamme anupamme commented Sep 7, 2026

Copy link
Copy Markdown

Summary

Fix high severity security issue in Email/Sender/Transport/OAuthBearerSMTP.pm.

Vulnerability

Field Value
ID V-001
Severity HIGH
Scanner multi_agent_ai
Rule V-001
File Email/Sender/Transport/OAuthBearerSMTP.pm:28
Assessment Likely exploitable
Chain Complexity 2-step

Description: The OAuthBearerSMTP.pm module accepts OAuth bearer tokens for SMTP authentication without implementing token binding, DPoP (Demonstrating Proof-of-Possession), or channel binding. The access_token is passed directly to the SMTP AUTH command without verification that the token is being used by the legitimate holder, allowing stolen tokens to be replayed from any location.

Evidence

Exploitation scenario: An attacker who obtains an OAuth bearer token via network sniffing, XSS in tmail web interface, or compromised client can replay the token to authenticate to the SMTP server from any location.

Scanner confirmation: multi_agent_ai rule V-001 flagged this pattern.

Production code: This file is in the production codebase, not test-only code.

Threat Model Context

This is a containerized service - vulnerabilities may be exploitable depending on network exposure.

Changes

  • Email/Sender/Transport/OAuthBearerSMTP.pm

Behavior Preservation

The change is scoped to 1 file on the vulnerable path.


Automated security fix by OrbisAI Security

Automated security fix generated by OrbisAI Security
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant