Skip to content
sooperset/mcp-atlassian·Indexed by this site · Originally published· Event →· Its place in the scan record →

mcp-atlassian fixes a credential misuse vulnerability in which HTTP transport does not validate Host and Origin under specific configurations

HTTP transports did not check Host and Origin while serving the operator's credentials

AI summary

mcp-atlassian released security advisory GHSA-qx98-vrcc-c5w9: versions before 0.24.5 do not validate the Host and Origin headers of requests under HTTP transport. When ALLOW_GLOBAL_CRED_FALLBACK=true or IGNORE_HEADER_AUTH=true, the server responds to requests without credentials using the operator's own Atlassian credentials; a browser web page able to reach that listening port can send such requests via DNS rebinding, thereby reading data the operator can read and invoking write tools, unless READ_ONLY_MODE or tool filters block it. Deployments that do not enable these two settings and stdio deployments are unaffected. The issue was found by the project's internal security audit.

Read originalgithub.com