mcp-atlassian 0.14.3

Direct Vulnerabilities

Known vulnerabilities in the mcp-atlassian package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H Directory Traversal mcp-atlassian is a The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include: Affected versions of this package are vulnerable to Directory Traversal via the `confluence_upload_attachment` process. An attacker can access and exfiltrate arbitrary files that the server process can read by supplying crafted file paths, including sensitive files such as environment variables or private keys, which may lead to exposure of credentials and other confidential information. This can be exploited by any authenticated client or by manipulating an AI agent through prompt injection, allowing an attacker to trigger file exfiltration without direct access. How to fix Directory Traversal? Upgrade `mcp-atlassian` to version 0.22.0 or higher.	[,0.22.0)
H External Control of File Name or Path mcp-atlassian is a The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include: Affected versions of this package are vulnerable to External Control of File Name or Path via the `upload_attachment` process. An attacker can access and exfiltrate arbitrary files from the server's filesystem, including sensitive configuration and credential files, by supplying crafted file paths that are resolved and read on the server. This is only exploitable if the deployment uses remote or HTTP-based transports, as in local single-user deployments the file path refers to the user's own files. How to fix External Control of File Name or Path? Upgrade `mcp-atlassian` to version 0.22.0 or higher.	[,0.22.0)
H Server-side Request Forgery (SSRF) mcp-atlassian is a The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include: Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the `validate_url_for_ssrf` process. An attacker can access internal resources or sensitive information by exploiting a DNS rebinding race condition between hostname validation and connection time resolution. This is only exploitable if an attacker can control a DNS server to rapidly rebind the hostname between validation and connection. How to fix Server-side Request Forgery (SSRF)? Upgrade `mcp-atlassian` to version 0.22.0 or higher.	[,0.22.0)
M Server-side Request Forgery (SSRF) mcp-atlassian is a The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include: Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the HTTP endpoint. An attacker can cause the server to make arbitrary outbound HTTP requests to attacker-controlled URLs, potentially exposing sensitive internal resources or credentials, by sending specially crafted requests containing `X-Atlassian-Jira-Url` or `X-Atlassian-Confluence-Url` headers without an `Authorization` header. Note: This is only exploitable if the server is running with `--transport streamable-http` or `--transport sse`, the request contains both the relevant URL and personal token headers, and no `Authorization` header is present. How to fix Server-side Request Forgery (SSRF)? Upgrade `mcp-atlassian` to version 0.17.0 or higher.	[,0.17.0)
M External Control of File Name or Path mcp-atlassian is a The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include: Affected versions of this package are vulnerable to External Control of File Name or Path via the `confluence_download_attachment` MCP tool. An attacker can write arbitrary files to any location accessible by the server process and potentially achieve code execution by supplying a crafted `download_path` parameter and uploading a malicious attachment. How to fix External Control of File Name or Path? Upgrade `mcp-atlassian` to version 0.17.0 or higher.	[,0.17.0)

Vulnerability

Vulnerable Version

Directory Traversal

mcp-atlassian is a The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include:

Affected versions of this package are vulnerable to Directory Traversal via the confluence_upload_attachment process. An attacker can access and exfiltrate arbitrary files that the server process can read by supplying crafted file paths, including sensitive files such as environment variables or private keys, which may lead to exposure of credentials and other confidential information. This can be exploited by any authenticated client or by manipulating an AI agent through prompt injection, allowing an attacker to trigger file exfiltration without direct access.

How to fix Directory Traversal?

Upgrade mcp-atlassian to version 0.22.0 or higher.

[,0.22.0)

External Control of File Name or Path

Affected versions of this package are vulnerable to External Control of File Name or Path via the upload_attachment process. An attacker can access and exfiltrate arbitrary files from the server's filesystem, including sensitive configuration and credential files, by supplying crafted file paths that are resolved and read on the server. This is only exploitable if the deployment uses remote or HTTP-based transports, as in local single-user deployments the file path refers to the user's own files.

How to fix External Control of File Name or Path?

Upgrade mcp-atlassian to version 0.22.0 or higher.

[,0.22.0)

Server-side Request Forgery (SSRF)

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the validate_url_for_ssrf process. An attacker can access internal resources or sensitive information by exploiting a DNS rebinding race condition between hostname validation and connection time resolution. This is only exploitable if an attacker can control a DNS server to rapidly rebind the hostname between validation and connection.

How to fix Server-side Request Forgery (SSRF)?

Upgrade mcp-atlassian to version 0.22.0 or higher.

[,0.22.0)

Server-side Request Forgery (SSRF)

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the HTTP endpoint. An attacker can cause the server to make arbitrary outbound HTTP requests to attacker-controlled URLs, potentially exposing sensitive internal resources or credentials, by sending specially crafted requests containing X-Atlassian-Jira-Url or X-Atlassian-Confluence-Url headers without an Authorization header.

Note:

This is only exploitable if the server is running with --transport streamable-http or --transport sse, the request contains both the relevant URL and personal token headers, and no Authorization header is present.

How to fix Server-side Request Forgery (SSRF)?

Upgrade mcp-atlassian to version 0.17.0 or higher.

[,0.17.0)

External Control of File Name or Path

Affected versions of this package are vulnerable to External Control of File Name or Path via the confluence_download_attachment MCP tool. An attacker can write arbitrary files to any location accessible by the server process and potentially achieve code execution by supplying a crafted download_path parameter and uploading a malicious attachment.

How to fix External Control of File Name or Path?

Upgrade mcp-atlassian to version 0.17.0 or higher.

[,0.17.0)

mcp-atlassian@0.14.3

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically