Headline

GHSA-hq4h-w933-jm6c: khoj has an IDOR in subscription management allows unauthorized subscription modifications

Summary

An Insecure Direct Object Reference (IDOR) vulnerability in the update_subscription endpoint allows any authenticated user to manipulate other users’ Stripe subscriptions by simply modifying the email parameter in the request.

Details

The vulnerability exists in the subscription endpoint at /api/subscription. The endpoint uses an email parameter as a direct reference to user subscriptions without verifying object ownership. While authentication is required, there is no authorization check to verify if the authenticated user owns the referenced subscription.

Vulnerable code in /api/subscription:

@subscription_router.patch("")
@requires(["authenticated"])
async def update_subscription(request: Request, email: str, operation: str):
    # IDOR: email parameter directly references user subscriptions without ownership verification
    customers = stripe.Customer.list(email=email).auto_paging_iter()
    customer = next(customers, None)
    
    if operation == "cancel":
        # Any authenticated user can modify any subscription referenced by email
        customer_id = customer.id
        for subscription in stripe.Subscription.list(customer=customer_id):
            stripe.Subscription.modify(subscription.id, cancel_at_period_end=True)

PoC

Create a customer account in stripe:
- Customer A: [email protected] (attacker)
Log in as any user.
Send this request:

PATCH /api/[email protected]&operation=cancel HTTP/1.1

The subscription for Customer A is successfully set to cancel.

Impact

High: Revenue loss via mass cancellation of subscriptions. Loss of customer trust by re-enabling subscriptions they had set to cancel.

Resolution

This was fixed in the following commit which limited subscription update operations to the authenticated user: https://github.com/khoj-ai/khoj/commit/47d3c8c23597900af708bdc60aced3ae5d2064c1. Support for arbitrarily presenting an email for update has been deprecated.

6 months ago

ghsa

Open in Source

#vulnerability #git #auth

Summary

Details

The vulnerability exists in the subscription endpoint at /api/subscription. The endpoint uses an email parameter as a direct reference to user subscriptions without verifying object ownership. While authentication is required, there is no authorization check to verify if the authenticated user owns the referenced subscription.

Vulnerable code in /api/subscription:

@subscription_router.patch(“”) @requires([“authenticated”]) async def update_subscription(request: Request, email: str, operation: str): # IDOR: email parameter directly references user subscriptions without ownership verification customers = stripe.Customer.list(email=email).auto_paging_iter() customer = next(customers, None)

if operation \== "cancel":
    \# Any authenticated user can modify any subscription referenced by email
    customer\_id \= customer.id
    for subscription in stripe.Subscription.list(customer\=customer\_id):
        stripe.Subscription.modify(subscription.id, cancel\_at\_period\_end\=True)

PoC

Create a customer account in stripe:
- Customer A: [email protected] (attacker)
Log in as any user.
Send this request:

PATCH /api/[email protected]&operation=cancel HTTP/1.1

The subscription for Customer A is successfully set to cancel.

Impact

High:
Revenue loss via mass cancellation of subscriptions.
Loss of customer trust by re-enabling subscriptions they had set to cancel.

Resolution

This was fixed in the following commit which limited subscription update operations to the authenticated user: khoj-ai/khoj@47d3c8c. Support for arbitrarily presenting an email for update has been deprecated.

References