Shipt: Api Token Leaked in [shoppers.shipt.com]

A researcher reported an API key stored in source code that was part of a 3rd party knowledge base integration. The Shipt information security team immediately investigated the report and determined that the API key referenced was a legacy token that was no longer being used. While it didn't...

Shipt: bypass the [OKTA] login redirect can lead to disclosing limited-information about the sub-domain at [ shiptsec.com ]

A security researcher identified limited and non-sensitive information disclosure for one of our public-facing tools that is used by internal users. While the risk was very low and nothing was directly exploitable, we went ahead and made the quick change to mitigate this behavior. We made the...

Shipt: Slack token leaking in stackoverflow and devtimes

A Shipt employee inadvertently posted a Slack Webhook URI including the authentication token on two public tech forums: Stackoverflow.com and devtimes.com. While this incoming webhook's configuration was restricted to posting in a single channel created for testing this application and only 2 Shi...

Shipt: Subdomain takeover at segway.shipt.com

A security researcher identified a stale DNS record that pointed to a legacy 3rd party service. This allowed for a subdomain takeover, which the researcher provided a well written and detailed Proof of Concept POC. Shipt's security team acted immediately to validate the vulnerability and remove t...

Shipt: Any user can completely delete their own account without authorization and/or going through any kind of membership cancellation protocol.

A security researcher identified an endpoint that allowed Shipt Members to delete their own account by intercepting an HTTP request, changing the HTTP method to DELETE, and forwarding the request, bypassing the normal membership cancellation protocol. This endpoint did not allow for modifying oth...

Shipt: Open redirect on marketing site

Security researcher identified an open redirect vulnerability in www.shipt.com. Shipt's security and engineering teams quickly responded and addressed the issue...