Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: 'herd site list' exposes credentials?

未关闭
#1,789 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
security

调研方向

The report concerns whether herd site list exposed local .env contents in Herd v2.0.0; it gives no reproduction steps or code entry point. First verify the command's behavior in the affected version and compare it with v2.0.3. Done means confirming whether credentials were exposed and identifying any relevant fix or release information.

由索引模型根据 Issue 内容生成。

描述

fixed-in-next-release macOS
Platform

macOS

Operating system version

macOS 27 Golden Gate

System architecture

ARM64 (M1, M2, etc)

Herd Version

2.0.0

PHP Version

No response

Bug description

After just upgrading to Herd v2, we got an alert from Claude that claimed running 'herd site list' dumped every local site's full .env into the transcript, thus needed to rotate all keys.

Before we could run 'herd site list' locally again to verify what happened, we were automatically upgraded to v2.0.3 which does not appear to have the issue.

Tried to look at the changelog to verify any patches related to this, but there doesn't seem to be any information about releases between v2.0.0 and v2.0.3.

Can someone please chime in on whether this is a major concern?

Steps to reproduce

No response

Relevant log output
Directly from Claude:

Also: my herd site list call dumped every local site’s full .env into this transcript, including API keys for [REDACTED] and others. I only needed the site paths and didn’t anticipate it returning file contents. Nothing left your machine, but if this transcript gets shared or exported, treat those credentials as exposed. I won’t use that action again.

I need to be straight with you rather than reassuring: deleting the transcript does not undo the exposure. The only reliable fix is rotation.

Here’s the accurate picture:
1. It already went to the API. That tool result entered my context, which means it was transmitted to Anthropic as part of this conversation. Deleting anything locally doesn’t reach that. Anthropic’s retention policy governs it from here.
2. Worse: every further message in this session re-sends it. My context includes that dump, so each turn we exchange retransmits all of it. Stop using this session. That’s the single most effective thing you can do right now.

The actual remediation is rotation. Treat these as compromised
主要语言
没有语言数据
星标
124
派生
1
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

beyondcode/herd-community 的其他 Issue

查看 beyondcode/herd-community 的全部 Issue

相似的 Issue

更多 Security Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。