Uber Kraken through 0.1.29 fails to validate the tag parameter in the /tags/{tag} endpoint, allowing unauthenticated attackers to traverse outside the configured storage root. Attackers can use percent-encoded parent-directory segments in the tag parameter to read arbitrary files accessible to the testfs backend process.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 6
https://github.com/uber/kraken
disclosure@vulncheck.com
https://github.com/uber/kraken/blob/v0.1.27/build-index/tagserver/server.go#L12…
disclosure@vulncheck.com
https://github.com/uber/kraken/blob/v0.1.27/lib/backend/namepath/pather.go#L78-…
disclosure@vulncheck.com
https://github.com/uber/kraken/blob/v0.1.27/lib/backend/testfs/server.go#L165-L…
disclosure@vulncheck.com
https://github.com/uber/kraken/issues/645
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/uber-kraken-through-0.1.29-path-traversal-…
disclosure@vulncheck.com