Products / mcp-atlassian
mcp-atlassian
30 records.
- MCP Atlassian: Arbitrary File Read & Exfiltration (Confused Deputy) in JIRA update_issue An MCP tool passes agent-supplied absolute paths straight to an upload call, so the privileged server reads restricted host files and attaches them to a ticket.
- MCP Atlassian: ENABLED_TOOLS / Toolset authorization bypass Tool filters are applied only when listing tools, so a direct tools/call request can invoke any registered tool by name, bypassing the configured restriction.
- MCP Atlassian: Insecure File Permissions on OAuth Token Storage The MCP server writes OAuth tokens to a file with default permissions, so other local users can read the Atlassian credentials.
- MCP Atlassian: SSRF via DNS Rebinding in Header-Based Authentication Flow The header-based auth flow validates a Jira URL's DNS result, then the later request resolves again, so a rebinding host reaches internal addresses.
- mcp-atlassian has an incomplete SSRF remediation The MCP middleware accepts Jira and Confluence base URLs from request headers without validation, so the server fetches attacker-chosen internal hosts.
- MCP Atlassian: SSRF redirect protection missing for basic-auth and OAuth authentication branches The SSRF redirect check is attached only to the header token auth branch, so basic-auth and OAuth requests follow redirects to internal addresses such as cloud metadata.
- MCP Atlassian: Arbitrary file read via confluence_upload_attachment allows exfiltration of server credentials The Confluence upload tool opens any caller-supplied local path without checks, letting a client attach server files such as credentials to a page.
- MCP Atlassian: Incomplete path traversal fix allows intra-CWD module overwrite and RCE (bypass of GHSA-xjgw-4wvw-rgm4) An incomplete traversal fix still lets attachment downloads overwrite application source modules in the working directory, so injected code runs on restart.
- MCP Atlassian: Arbitrary file read/exfiltration via upload_attachment missing validate_safe_path() The MCP attachment upload tool sends local files to Confluence without the path check its download methods use, so an agent can be steered to read any file.
- MCP Atlassian: Unauthenticated arbitrary local file read via upload_attachment file_path, chained with missing auth on streamable-http transport Omitting the Authorization header lets unauthenticated clients call MCP tools, and an upload tool then reads any server file path and exposes its contents.
- MCP Atlassian: Arbitrary File Read via Upload Attachment Tools The upload attachment tools accept arbitrary server file paths without the safe-path check, letting an MCP client or an assistant steered by injected content exfiltrate files.
- MCP Atlassian: Arbitrary local file READ via unconstrained file_path in upload_attachment (Confluence + Jira) The Confluence and Jira attachment upload tools open any local path supplied to them and upload its contents, with no base-directory restriction.
- MCP Atlassian: Arbitrary server-local file upload to Jira/Confluence attachments via unrestricted file_path parameters MCP attachment upload tools take caller-supplied local paths, read those files from the server, and upload them to Jira or Confluence without restriction.
- MCP Atlassian: Reflected XSS in OAuth Setup Callback Handler The local OAuth callback server of an MCP integration echoes the error query parameter into HTML unescaped, so a crafted link runs script in the browser.
- MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions
- MCP Atlassian: Path traversal in upload_attachment allows arbitrary file read (incomplete fix for CVE-2026-27825)
- MCP Atlassian: SSRF Protection Bypass
- MCP Atlassian: Path traversal in upload_attachment allows arbitrary file read and exfiltration via MCP tool call
- MCP Atlassian: HTTP upload tools accept arbitrary server-local file paths
- MCP Atlassian: Path Traversal / Arbitrary File Read in confluence_upload_attachment MCP tool (incomplete fix of GHSA-xjgw-4wvw-rgm4)
- MCP Atlassian: Incomplete fix for GHSA-7r34-79r5-rcc9: redirect-based SSRF via unhooked requests session in Jira user-permission lookup
- MCP Atlassian: Jira and Confluence attachment upload tools can read arbitrary server-local files
- MCP Atlassian: JIRA_PROJECTS_FILTER / CONFLUENCE_SPACES_FILTER allow forbidden-project content exfiltration (one LIVE-proven on Atlassian Cloud)
- [mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token
- MCP Atlassian: MCP HTTP Client Server-Local File Exfiltration via Unvalidated Attachment Upload Path
- MCP Atlassian: DNS-rebinding TOCTOU bypass of the SSRF fix (CVE-2026-27826) The MCP server validates a header-supplied host's DNS result but later re-resolves it at connect time, so a rebinding name reaches internal addresses.
- mcp-atlassian: Arbitrary file read via missing path validation in confluence_upload_attachment
- mcp-atlassian: Arbitrary server-side file read via attachment upload
- MCP Atlassian has SSRF via unvalidated X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url headers Unauthenticated requests carrying custom URL headers make the MCP server send requests to attacker-chosen URLs, including internal metadata services.
- MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachment