Skip to content

Merge Develop into Release#3757

Closed
r2c-argo[bot] wants to merge 13 commits intoreleasefrom
merge-develop-to-release
Closed

Merge Develop into Release#3757
r2c-argo[bot] wants to merge 13 commits intoreleasefrom
merge-develop-to-release

Conversation

@r2c-argo
Copy link
Copy Markdown
Contributor

@r2c-argo r2c-argo bot commented Feb 28, 2026

Created automatically with the Argo bot using the Argo workflow in release-workflow.yaml

kurt-r2c and others added 10 commits September 23, 2025 15:09
* fix for CODE-9032

* add test
## Link to an issue, if relevant

(internal Slack thread)

### ~~Adding a new~~ Revising a rule? Look over this PR checklist

- The issue or PR has links, references, or examples.
- The rule has **true positive** and **true negative** test cases in a file that matches the rule name.

> If the rule is `my-rule`, the test file name should be `my-rule.js`.
>
> True positives are marked by comments with `ruleid: <my-rule>` and true negatives are marked by comments with `ok: <my-rule>`.

- The rule has a good message. A good message includes:

> 1. A description of the pattern (e.g., missing parameter, dangerous flag, out-of-order function calls).
> 1. A description of why this pattern was detected (e.g., logic bug, introduces a security vulnerability, bad practice).
> 1. An alternative that resolves the issue (e.g., use another function, validate data first, discard the dangerous flag).
This updates aws-cloudfront-insecure-tls rule
to account for the addition of aws cloudfront
support for TLSv1.2_2025 and TLSv1.3_2025
Co-authored-by: Pieter De Cremer <pieter@Mac.localdomain>
Co-authored-by: Pieter De Cremer <pieter@Mac.localdomain>
A GitHub Action may still be vulnerable when a more complicated pattern is used, like an || operator.
* Add owasp 2025 mapping

* fix metadata of twilio twiml injection rule

---------

Co-authored-by: Pieter De Cremer <pieter@Mac.localdomain>
Removed reference to github.com/ravisastryk/go-safeinput for automatic protection in the warning message about unsafe deserialization.
| exception Not_found -> 3
try
(* ruleid:hashtbl-find-outside-try *)
if Hashtbl.find h 1
Copy link
Copy Markdown

@semgrep-zcs-prod-semgrep semgrep-zcs-prod-semgrep bot Feb 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'Hashtbl.find' raises the 'Not_found' exception. Handle the exception or use 'Hashtbl.find_opt' instead. If you have proof that the key exists in the table, use 'assert false' as the exception handler to demonstrate awareness of the issue. If your code uses the syntax 'match Hashtbl.find ... with exception Not_found -> ...', it's fine and we apologize for not detecting it. Consider using 'Hashtbl.find_opt' to please Semgrep and stay safe.

🌟 Removed in commit 180e65d 🌟

jmgrosen and others added 3 commits March 4, 2026 13:10
Several Java and Go test files for rules had duplicate names where they
weren't actually allowed by the language. This caused issues for naming
in Semgrep, which assumes that this should be impossible.

This commit replaces those duplicate names with distinct names.
Disambiguate duplicate function/method names that lead to odd
shadowing of results. All the actual matches are preserved.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@LewisArdern LewisArdern self-requested a review March 25, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants