Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62647: CWE-863 Incorrect Authorization in Restaurant Brands International assistant platform

0
Medium
VulnerabilityCVE-2025-62647cvecve-2025-62647cwe-863
Published: Fri Oct 17 2025 (10/17/2025, 00:00:00 UTC)
Source: CVE Database V5
Vendor/Project: Restaurant Brands International
Product: assistant platform

Description

The Restaurant Brands International (RBI) assistant platform through 2025-09-06 provides the functionality of returning a JWT that can be used to call an API to return a signed AWS upload URL, for any store's path.

AI-Powered Analysis

AILast updated: 10/17/2025, 21:03:02 UTC

Technical Analysis

CVE-2025-62647 is an authorization vulnerability classified under CWE-863 affecting the Restaurant Brands International (RBI) assistant platform. The platform provides functionality that returns a JSON Web Token (JWT) enabling API calls to obtain signed AWS upload URLs for store-specific paths. Due to incorrect authorization logic, the platform issues JWTs without verifying whether the requester is authorized to access or upload data to the specified store path. This flaw allows an unauthenticated attacker to generate valid upload URLs for any store path, bypassing intended access controls. The vulnerability impacts the integrity of the system by potentially allowing unauthorized data uploads or modifications to store-related resources hosted on AWS. The CVSS 3.1 base score is 5.8 (medium), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and a scope change due to crossing security boundaries. Confidentiality and availability are not directly affected, but the integrity impact is significant. No patches or known exploits are currently reported, indicating the vulnerability is newly disclosed. The assistant platform likely supports operational workflows for RBI’s retail stores, making the vulnerability relevant for supply chain and operational security. Attackers exploiting this flaw could manipulate store data, upload malicious content, or interfere with store operations by leveraging the AWS upload URLs. The lack of authentication and user interaction requirements increases the risk of automated exploitation. The vulnerability highlights the importance of robust authorization checks in token issuance and API access control, especially when dealing with cloud storage services and multi-tenant environments.

Potential Impact

For European organizations operating or franchising RBI stores, this vulnerability poses a risk of unauthorized data manipulation within the assistant platform’s AWS storage environment. Attackers could upload malicious files, alter store-specific data, or disrupt operational workflows, potentially leading to supply chain integrity issues or reputational damage. Although confidentiality and availability are not directly impacted, integrity compromise can affect business processes, customer trust, and compliance with data protection regulations such as GDPR if personal or operational data is altered. The vulnerability’s network accessibility and lack of authentication requirements increase the likelihood of exploitation attempts, especially in countries with significant RBI retail presence. Disruption or manipulation of store data could also have cascading effects on inventory management, order processing, or customer-facing services. European entities relying on this platform should consider the operational and regulatory implications of unauthorized data changes and prepare incident response plans accordingly.

Mitigation Recommendations

1. Implement strict authorization checks during JWT issuance to ensure tokens are only granted for store paths the requester is authorized to access. 2. Enforce fine-grained access control on the API that provides signed AWS upload URLs, validating user permissions and store ownership. 3. Introduce logging and monitoring of all API requests for upload URLs, with alerts for anomalous or bulk requests targeting multiple or unauthorized store paths. 4. Apply network segmentation and API gateway policies to restrict access to the assistant platform’s APIs to trusted internal or authenticated clients. 5. Conduct regular security audits and penetration testing focusing on authorization logic and token management. 6. Once available, promptly apply vendor patches or updates addressing this vulnerability. 7. Educate development and operations teams on secure token handling and the risks of improper authorization. 8. Review AWS S3 bucket policies and signed URL expiration times to minimize the window of opportunity for misuse. 9. Prepare incident response procedures to quickly identify and remediate any unauthorized uploads or data tampering events.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2025-10-17T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68f2ab359c34d0947f42a467

Added to database: 10/17/2025, 8:46:45 PM

Last enriched: 10/17/2025, 9:03:02 PM

Last updated: 10/19/2025, 2:32:32 PM

Views: 13

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats