Announcing MCP Toolbox Java SDK v1.0: Agentic data access for the enterprise
cloud.google.com·6d ago
Cloud & Infrastructure
The New Stack·Aug 28·5 min read
JetBrains told everyone to patch. It didn’t patch itself.
TL;DR
JetBrains has urged users to rotate credentials after a critical vulnerability in its TeamCity server was exploited, revealing that its own server remained unpatched. This oversight raises significant security concerns for users relying on the Cadence cloud development service.
✦ Why It Matters
Immediately check and patch your TeamCity servers to prevent unauthorized access and potential data breaches.
Key Takeaways
- Rotate all credentials used in Cadence during the affected period.
- Audit source control logs for unauthorized changes or access.
- Check cloud environments for unexpected IAM changes or new accounts.
- Review artifacts produced during the breach for integrity.
How It Works
The vulnerability in TeamCity allows attackers to execute arbitrary commands on the server, compromising the entire development environment. This central role in CI/CD systems makes them attractive targets for attackers.