Skip to content

feat: add Rancher/Cattle token detector#4874

Open
moeedrehman135 wants to merge 4 commits intotrufflesecurity:mainfrom
moeedrehman135:feat/rancher-token-detector
Open

feat: add Rancher/Cattle token detector#4874
moeedrehman135 wants to merge 4 commits intotrufflesecurity:mainfrom
moeedrehman135:feat/rancher-token-detector

Conversation

@moeedrehman135
Copy link
Copy Markdown

@moeedrehman135 moeedrehman135 commented Apr 8, 2026

Summary

Adds a detector for Rancher/Cattle API tokens as requested in #4622.

Changes

  • New detector in pkg/detectors/rancher/
  • Regex matches CATTLE_TOKEN, RANCHER_TOKEN, CATTLE_BOOTSTRAP_PASSWORD, RANCHER_API_TOKEN patterns
  • Requires server context (CATTLE_SERVER or RANCHER_URL) nearby to reduce false positives
  • HTTP verification against Rancher v3 API
  • Pattern tests included
  • Registered in defaults.go

Testing

All pattern tests pass:

  • Valid token with server context
  • Invalid token (too short)
  • Token without server context (should not detect)

Closes #4622


Note

Medium Risk
Adds a new secret detector with optional live HTTP verification and wires it into the default scanner set, which can affect scan results and introduce outbound network calls when verification is enabled. Also updates the shared detectors.proto/generated pb enum (DetectorType) to include Rancher, a broad interface change that could impact consumers if mismatched across builds.

Overview
Adds a new rancher detector that only reports Rancher/Cattle tokens when a CATTLE_SERVER/RANCHER_URL is present, and can optionally verify candidates by calling GET /v3 with a bearer token.

Registers the detector in pkg/engine/defaults/defaults.go and extends detectors.proto/detectors.pb.go with DetectorType_Rancher so results are typed correctly, with accompanying pattern tests and benchmarks.

Reviewed by Cursor Bugbot for commit f031603. Bugbot is set up for automated code reviews on this repo. Configure here.

@moeedrehman135 moeedrehman135 requested a review from a team April 8, 2026 14:42
@moeedrehman135 moeedrehman135 requested review from a team as code owners April 8, 2026 14:42
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 8, 2026

CLA assistant check
All committers have signed the CLA.

var (
tokenPattern = regexp.MustCompile(
`(?i)(?:CATTLE_TOKEN|RANCHER_TOKEN|CATTLE_BOOTSTRAP_PASSWORD|RANCHER_API_TOKEN)[^\w]{1,4}([a-z0-9]{54,64})`,
)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Token regex won't match real Rancher token format

High Severity

Real Rancher API tokens use the format token-xxxxx:yyyyyyyyyy (containing hyphens and colons), as documented in Rancher's official API docs. The capture group [a-z0-9]{54,64} only allows lowercase alphanumerics, so it will never match actual CATTLE_TOKEN or RANCHER_TOKEN values. The test data uses a fabricated token (kubeadmin5f8a3b...) that doesn't resemble any real Rancher token format, masking this fundamental mismatch.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 86cc6fa. Configure here.

- Add regex pattern for CATTLE_TOKEN/RANCHER_API_TOKEN format
- Require server context (CATTLE_SERVER/RANCHER_URL) to reduce false positives
- Add HTTP verification against Rancher v3 API
- Add pattern tests
- Register detector in defaults.go

Closes trufflesecurity#4622
@moeedrehman135 moeedrehman135 force-pushed the feat/rancher-token-detector branch from 86cc6fa to 74f5a74 Compare April 8, 2026 15:05
"github.com/trufflesecurity/trufflehog/v3/pkg/pb/detectorspb"
)

type Scanner struct{}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Missing multi-part credential provider causes missed detections

Medium Severity

The Scanner struct doesn't embed detectors.DefaultMultiPartCredentialProvider, even though the detector requires two distinct patterns (server context via serverPattern and secret via tokenPattern) to co-occur in the same data chunk. Without this, the Aho-Corasick span calculator uses its default 512-byte radius, so if the server URL and token are farther apart in the scanned data, the chunk delivered to FromData may lack one of the two patterns, causing valid credentials to be silently missed. All comparable multi-part detectors (e.g., mattermostpersonaltoken, formsite) embed this provider.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 74f5a74. Configure here.

req.Header.Set("Authorization", "Bearer "+token)
res, err := client.Do(req)
if err == nil {
defer res.Body.Close()
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Deferred body close accumulates in loop iterations

Medium Severity

The defer res.Body.Close() is inside a for loop, so response bodies won't be closed until FromData returns rather than at the end of each iteration. This accumulates open connections/file descriptors across iterations. A comparable detector (pivotaltracker) with nearly identical structure correctly uses res.Body.Close() without defer in its loop.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 7401a70. Configure here.

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 2 potential issues.

There are 5 total unresolved issues (including 3 from previous reviews).

Fix All in Cursor

Reviewed by Cursor Bugbot for commit f031603. Configure here.

message GitHubSSHKey {
string user = 1;
string public_key_fingerprint = 2;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Proto file contains duplicate content causing compilation failure

High Severity

The proto/detectors.proto file has been corrupted — a second complete proto file definition (with duplicate syntax, package, DecoderType enum, and all message types) is appended starting at line 1097. This will cause protoc compilation to fail with duplicate symbol errors whenever the proto is regenerated. The first copy also drops HTML = 5 from DecoderType, which is actively used in the codebase (e.g., pkg/decoders/html.go).

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit f031603. Configure here.

BASE64 = 2;
UTF16 = 3;
ESCAPED_UNICODE = 4;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Missing HTML decoder type in proto enum

High Severity

The DecoderType enum in the primary proto definition (lines 7–13) is missing HTML = 5, which existed in the original file. DecoderType_HTML is actively used by pkg/decoders/html.go and its tests. If the proto is regenerated from this file (after fixing the duplication issue), the HTML decoder type would be lost, breaking the HTML decoder.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit f031603. Configure here.

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.

Rancher Tokens

2 participants