Louis Vuitton Malletier Public Bug Bounty Program

About Us

Louis Vuitton Malletier, commonly known as Louis Vuitton is a French fashion house and luxury goods company founded in 1854 by Louis Vuitton. The label's LV monogram appears on most of its products, ranging from luxury trunks and leather goods to ready-to-wear, shoes, watches, jewellery, accessories, sunglasses and books. Louis Vuitton is one of the world's leading international fashion houses; it sells its products through standalone boutiques, lease departments in high-end department stores, and through the e-commerce section of its website.

Program Rules

About the scope of this program

Regarding https://[it | fr | us | sg | …].louisvuitton.com, our program is limited to our e-commerce web application and its API. You may hunt on all country locals linked to *.louisvuitton.com (e.g. fr.louisvuitton.com, us.louisvuitton.com, au.louisvuitton.com, ...) but other subdomains are out of the scope of this program. You may refer to the following page which lists our country locals : https://eu.louisvuitton.com/dispatch?noDRP=true.

In addition to the ecommerce scope mentioned above you're welcome to test api.louisvuitton.com and other subdomains of *.api.louisvuitton.com, the rest of *.louisvuitton.com is to be considred as out of scope.

** We ask you to respect the scope of our program and to don't hunt outside of it. Should you need to report anything outside of the scope of this program you may do so through our VDP program here https://vdp.louisvuitton.com.**

Regarding Systemic Issues

A common framework is deployed across all our country locals which means that if you find an issue rooted in this framework or shared ressrouces it'll likely be applicable to other country versions. In such a case, these issues won't be considered as systemic and would be closed as duplicate/informative since a single fix at the framework/ressource level will allow us to address it across all country locals.

For other situations the systemic issues rules will be applied as usual.

Temporary exclusion on *.jsp

XSS and similar issues (e.g. open redirect, CSRF, HTMLi) will be considered as non qualifying issues for the time being on *.jsp for https://[it | fr | us | sg | …].louisvuitton.com.

Testing Policy and Responsible Disclosure

Please adhere to the following rules while performing research on this program:

• Denial of service (DoS) attacks on our applications, servers, networks or infrastructure are strictly forbidden.

• Avoid tests that could cause degradation or interruption of our services.

• Do not use automated scanners or tools that generate large amount of network traffic.

• Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.

• Do not copy any files from our applications/servers and disclose them.

• No vulnerability disclosure, full, partial or otherwise, is allowed.

Important precautions and limitations

As a complement to the Program's rules and testing policy:

• DO NOT alter compromised accounts by creating, deleting or modifying any data

• DO NOT use compromised accounts to search for post-auth vulnerabilities (they won't be eligible anyway)

• DO NOT include Personally Identifiable Information (PII) in your report and please REDACT/OBFUSCATE the PII that is part of your PoC (screenshot, server response, JSON file, etc.) as much as possible.

• In case of exposed credentials or secrets, limit yourself to verifying the credentials validity

• In case of sensitive information leak, DO NOT extract/copy every document or data that is exposed and limit yourself to describe and list what is exposed.

Scopes

Out of Scope

• All domains, subdomains or assets not listed in the above list of 'Scopes' must be considered as out of the scope of this program
• *.louisvuitton.com (except those explicitly listed)

Vulnerability Types

Qualifying vulnerabilities

• SQL Injection (SQLi)
• Cross-Site Scripting (XSS)
• Remote Code Execution (RCE)
• Insecure Direct Object Reference (IDOR)
• Horizontal and vertical privilege escalation
• Authentication bypass & broken authentication
• Business Logic Errors vulnerability with real security impact
• Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
• Cross-Origin Resource Sharing (CORS) with real security impact
• Cross-site Request Forgery (CSRF) with real security impact
• Open Redirect
• Exposed secrets, credentials or sensitive information on an asset under our control and affecting at least one of our scopes

Non-qualifying vulnerabilities

• Broken Link/Social media Hijacking
• Tabnabbing
• Missing cookie flags
• Content/Text injections
• Clickjacking/UI redressing
• Denial of Service (DoS) attacks
• Recently disclosed CVEs (less than 30 days sinces patch release)
• CVEs without exploitable vulnerabilities and PoC
• Open ports or services without exploitable vulnerabilities and PoC
• Social engineering of staff or contractors
• Presence of autocomplete attribute on web forms
• Vulnerabilities affecting outdated browsers or platforms
• Self-XSS or XSS that cannot be used to impact other users
• Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
• SSL/TLS issues (e.g. expired certificates, best practices)
• Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
• Reports with attack scenarios requiring MITM or physical access to victim's device
• Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
• Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
• Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
• Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
• Disclosure of information without exploitable vulnerabilities and PoC (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets, EXIF Metadata, Origin IP)
• CSV injection
• Malicious file upload (e.g. EICAR files, .EXE)
• HTTP Strict Transport Security Header (HSTS)
• Subdomain takeover without a full exploitable vulnerability and PoC or not applicable to the scope
• Blind SSRF without exploitable vulnerabilities and PoC (e.g. DNS & HTTP pingback, Wordpress XMLRPC)
• Lack or bypass of rate-limiting, brute-forcing or captcha issues
• User enumeration (e.g. email, alias, GUID, phone number, common CMS endpoints)
• Weak password policies (e.g. length, complexity, reuse)
• Ability to spam users (email / SMS / direct messages flooding)
• Disclosed or misconfigured public API keys (e.g. Google Maps, Firebase, analytics tools...)
• Password reset token sent via HTTP referer to external services (e.g. analytics / ads platforms)
• Pre-account takeover (e.g. account creation via oAuth)
• GraphQL Introspection is enabled
• Task Hijacking
• Crashing your own application
• Lack of client-side protections on mobile binaries: SSL pinning/binary protection/code obfuscation/jailbreak detection/root detection/anti-debugging controls/ etc
• Lack of encryption on internal databases/preference files on mobile device
• Exploits that are only possible on Android versions that are not currently supported at the time of the emission of the vulnerability report
• Exploits that are only possible on IOS versions that are not currently supported at the time of the emission of the vulnerability report
• Exploits that are only possible on a jailbroken/rooted device
• Generic Android or iOS vulnerabilities
• Stolen secrets, credentials or information gathered from a third-party asset that we have no control over
• Exposed secrets, credentials or information on an asset under our control that are not applicable to the program's scope
• XSS and similar issues (e.g. open redirect, CSRF, HTMLi) on *.jsp for https://[it | fr | us | sg | …].louisvuitton.com.

Reports of leaks and exposed credentials

In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program's scope and policy.

Reward Eligibility and Amount

We are happy to thank everyone who submits valid reports which help us improve our security, however only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.

• The vulnerability must be a qualifying vulnerability (see above).

• The report must contain the following elements:

  • Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and our organisation, and remediation advice on fixing the vulnerability
  • Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
  • Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc

• You must not break any of the testing policy rules listed above.

• You must not be a former or current employee of our organisation or one of its contractors.

• If you find the same vulnerability several times, please create only one report and eventually use comments. You'll be rewarded according to your findings.

Reward amounts are based on:

• Reward grid of the report's scope
• CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

Reward Grid

Systemic Issues Reward Reduction

Hunting Requirements

User Agent

Please append to your user-agent header the following value: lvm-ywh-pbb.

Hunters Collaboration

When submitting new report, you can add up to 5 collaborators, and define the reward split ratio.

For more information, see the help center documentation on hunter collaboration.

Note: For reports that have already been rewarded, it is not possible to redistribute the rewards.