You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Severity: MediumDiscovered: 09 of July-2023, 01:24 PM
CWE ID
CWE-601
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Details
An http parameter may contain a URL value and could cause the web application to redirect the request to the specified URL. By modifying the URL value to a malicious site, an attacker may successfully launch a phishing scam and steal user credentials. Because the server name in the modified link is identical to the original site, phishing attempts have a more trustworthy appearance.
Possible exposure
Bypass Protection Mechanism; Gain Privileges or Assume Identity; Other
Remediation suggestions
Assume all input is malicious. Use an 'accept known good' input validation strategy, i.e., use a whitelist of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, 'boat' may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as 'red' or 'blue.' Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a blacklist). A blacklist is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. Use a whitelist of approved URLs or domains to be used for redirection.
Request
GET https://brokencrystals.com/brokencrystals.com?dummy=%2F HTTP/1.1Referer: https://brokencrystals.com/vendor/assets/vendor/Cookie: bc-calls-counter=1688908809109; connect.sid=4jbp_Wh6nJ3Hg8ukNy_VgTr6otWqR8Vj.QN%2FQF%2BUjM3GncnLMzIMEtxX%2FCKgRefkHDf1HXQ95I%2Bk; _csrf=4c8a7023d21380d6c1a48c2aaab823b9User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/106.0.5249.119 Safari/537.36Accept-Encoding: identityAuthorization: eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJ1c2VyIjoiYWRtaW4iLCJleHAiOjE2ODc4NTk4OTh9.HxGoTQ65t-PPh1IFc09X4_0YV0HiylDSpyA9zMu_J5S_-3tmp7nI3rOLmouVg4pUloF6fvtjOinZ8O44qM4DSMdNJOuJ698H__hFbRYO_7qAPf9WyBUo2XeIGVGhsu7aipvM_jAWQpa23IBrKYmO8-r4-nRZG-ZSjrEhMYGBpMYXl1vX5eL9qMUkZQpL8E717xoBc3S-aotrbht9LQJMBlhMT0Kt7esgCPkXaMuwg4eQCQ6yaxcGgToZbC6w7k671MZlJ17RNPH0w1C1YCbO4nYbncyAk1CLFPRcJ4eaWHCFhc4npJhSUEN2aEoLP2mLrRL8Dzrcpjn6K6dh3Lg6LDguklOx9RidTop6elKgrIqZA7rVabOGtDZGfd2eKIO0qZ-WR7xVN0oUIvVsnkEtTU_6j2Ly-PDl27fbS1l4eKSp1QSq3CW0NsQO1M4v324zi9ew4tSdFVKmNvEdfl-f3ei4raHC_qBJKOh4j0L8QipdTV1zY5gq_d70EZa3SwLUh-vJfEKPZxDnNThW9ytzMX86LZRdF5_gstL9A8HkJGdBY4Hhehdm7MpXalQ5VyMb_L1IdhUsLr_Iy81h6OFq_1yiLcSNk0y9zEOuoHryuxoukkjpmAeHBAbB9NyvSgD6gKR5IuEB4xgByOsVOPNt46TQHJVIlWrrBIhuXYApaSQUpgrade-Insecure-Requests: 1sec-ch-ua: "Not.A/Brand";v="8", "Chromium";v="114"sec-ch-ua-mobile: ?0sec-ch-ua-platform: "Windows"Content-Length: 0
Unvalidated Redirect
Severity:
MediumDiscovered:09 of July-2023, 01:24 PMCWE ID
CWE-601
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Details
An http parameter may contain a URL value and could cause the web application to redirect the request to the specified URL. By modifying the URL value to a malicious site, an attacker may successfully launch a phishing scam and steal user credentials. Because the server name in the modified link is identical to the original site, phishing attempts have a more trustworthy appearance.
Possible exposure
Bypass Protection Mechanism; Gain Privileges or Assume Identity; Other
Remediation suggestions
Assume all input is malicious. Use an 'accept known good' input validation strategy, i.e., use a whitelist of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, 'boat' may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as 'red' or 'blue.' Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a blacklist). A blacklist is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. Use a whitelist of approved URLs or domains to be used for redirection.
Request
Response
Screenshots
External links
The text was updated successfully, but these errors were encountered: