【高危】everos：路径穿越风险（GHSA-c795-2g9c-j48m）

安全情报快照 · 风险级别：高危 · CVSS：8.2 · GHSA-c795-2g9c-j48m

先看结论

everos存在路径穿越风险，<= 1.0.0 受影响，建议升级至 1.0.1。

影响范围

生态	组件	受影响版本	首个修复版本
pip	`everos`	<= 1.0.0	1.0.1

处置建议

优先将 everos 升级至 1.0.1 或更高版本；升级前请结合业务依赖完成兼容性验证。

上游技术详情（原文）

EverOS versions 1.0.0 and earlier are vulnerable to path traversal in the POST /api/v1/memory/add ingestion endpoint. The per-message sender_id field was not validated as a path-safe identifier (unlike app_id / project_id, which already enforced this). During user-memory extraction, sender_id is used as the owner_id and joined into the filesystem path where the extracted episode is persisted as a Markdown file. A sender_id containing ../ sequences could direct the write outside the configured memory root, allowing an unauthenticated caller to create or overwrite .md files at locations writable by the server process (unauthorized arbitrary file write). The file content is partially attacker-influenced.

Patch: Fixed in v1.0.1 with (1) path-safe validation on sender_id (character whitelist plus rejection of the . and .. tokens) and (2) a defense-in-depth containment check in the Markdown writer that rejects any write resolving outside the memory root before any filesystem access, covering both the write and the append read-modify-write paths.

Remediation: Upgrade to EverOS 1.0.1. There is no workaround for affected versions other than upgrading.

来源与许可

本页自动同步 GitHub Advisory Database 的公开数据，并保留上游原文供核验；不宣称原创分析。数据许可：CC-BY-4.0。