Skip to content

Add limit to JSON nesting depth #31069

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 6, 2025
Merged

Add limit to JSON nesting depth #31069

merged 3 commits into from
Aug 6, 2025

Conversation

biazmoreira
Copy link
Contributor

Description

Add limit to JSON nesting depth

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@biazmoreira biazmoreira requested a review from a team as a code owner June 23, 2025 14:17
@biazmoreira biazmoreira requested a review from guygrigsby June 23, 2025 14:17
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jun 23, 2025
Copy link

github-actions bot commented Jun 23, 2025

Build Results:
All builds succeeded! ✅

"strings"
)

func GenerateComplexJSON(depth int) string {
Copy link
Member

Choose a reason for hiding this comment

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

I don't see this being used. Seems like a great function to use in unit tests.

}

// This function avoids building the full map in memory, suitable for very deep JSON.
func calculateMaxDepthStreaming(jsonReader io.Reader) (int, error) {
Copy link
Member

Choose a reason for hiding this comment

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

We may be able to benefit from writing unit tests that use both generated JSON data and known challenging JSON data. That' s not to say the function is wrong, I don't think it is, rather to say it can't hurt to be sure.

Copy link

github-actions bot commented Jul 10, 2025

CI Results:
All Go tests succeeded! ✅

@biazmoreira biazmoreira force-pushed the biazmoreira/VAULT-36788 branch from 7719c10 to 70a50cd Compare August 6, 2025 10:15
Copy link

vercel bot commented Aug 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
vault-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 6, 2025 10:18am

@biazmoreira biazmoreira merged commit eedc2b7 into main Aug 6, 2025
93 checks passed
@biazmoreira biazmoreira deleted the biazmoreira/VAULT-36788 branch August 6, 2025 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants