Skip to content

Fix: hardcoded password in test and build-time dependency findings (Snyk) - #124

Open
reeshika-h wants to merge 1 commit into
developmentfrom
fix/snyk-hardcoded-passwords
Open

reeshika-h wants to merge 1 commit into
developmentfrom
fix/snyk-hardcoded-passwords

Conversation

@reeshika-h

Copy link
Copy Markdown
Contributor

Summary

Resolves DX-21542 (hardcoded password finding in a test) plus unticketed findings in test/build-time dependencies. Nothing shipped in the AAR changes.

  • TestError: the validation-error key password (arbitrary test data) is now title; the test still checks the same behaviour.
  • contentstack/build.gradle: extended the existing test-only resolutionStrategy block: bcprov 1.85 → 1.86, guava → 33.7.2-jre, asm → 9.11.1 (pulled in by Robolectric and the jacoco ant task).

Verification

  • snyk code test: 1 → 0. snyk test: security findings → 0; only the test-only junit EPL-1.0 licence note remains (no fix available).
  • Unit tests (JDK 17): 2141 run, 1 failure, identical to the baseline without this change.

🤖 Generated with Claude Code

Rename arbitrary password key in TestError; bump bcprov, guava and asm in the test-only resolutionStrategy block.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@reeshika-h
reeshika-h requested a review from a team as a code owner October 26, 2026 10:57
@snyk-io

snyk-io Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 7 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 0
  • Medium without fixes: 7
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

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.

1 participant