Repository navigation
Add security regression coverage and reporter credit - #5
Conversation
|
Hi Ronen, thanks for merging PR #5 and the SECURITY.md credit. You mentioned two GHSAs and CVEs were coming. I don't see them published yet. Is that still the plan? Happy to help write them. Anas |
|
@SyedAnas01 Both repository security advisories are now public, with your reporter credit and the verified affected/fixed release ranges:
The CVE requests were recorded on September 27; GitHub has not assigned CVE IDs as of this publication, so these are published GHSAs with CVE assignment still pending. Both distinguish the first fixed releases (0.2.2 / 0.3.0-beta.2) from the later recommended releases (0.2.3 / 0.3.0-beta.3). Thanks again for the private report and regression-test contribution. Your credit is included as Syed Anas Mohiuddin, Independent Researcher, Maintainer of mcp-safeguard. |
The classification and receipt fixes on main need broader regression coverage and the security reporter’s requested attribution. This adds tests for compound read/write names, ordinary read tools, proxy traversal and symlink rejection, and standalone receipt reads. SECURITY.md records the patched releases and credits Syed Anas Mohiuddin, Independent Researcher, Maintainer of mcp-safeguard.
Validation: all 90 tests pass on the reconciled branch; git diff --check passes. The PR changes only SECURITY.md and test/security-regressions.test.mjs relative to current main. Runtime code, version 0.3.0-beta.3, and the existing CI workflow remain as on main.