Open kinxjhyu opened 1 year ago
Risk Level | Number of Alerts |
---|---|
High | 0 |
Medium | 3 |
Low | 4 |
Informational | 9 |
Name | Risk Level | Number of Instances |
---|---|---|
CSP: Wildcard Directive | Medium | 6 |
Content Security Policy (CSP) Header Not Set | Medium | 1 |
Missing Anti-clickjacking Header | Medium | 1 |
Permissions Policy Header Not Set | Low | 7 |
Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s) | Low | 10 |
Strict-Transport-Security Header Not Set | Low | 10 |
X-Content-Type-Options Header Missing | Low | 4 |
Information Disclosure - Suspicious Comments | Informational | 1 |
Modern Web Application | Informational | 1 |
Re-examine Cache-control Directives | Informational | 3 |
Sec-Fetch-Dest Header is Missing | Informational | 3 |
Sec-Fetch-Mode Header is Missing | Informational | 3 |
Sec-Fetch-Site Header is Missing | Informational | 3 |
Sec-Fetch-User Header is Missing | Informational | 3 |
Storable and Cacheable Content | Informational | 6 |
Storable but Non-Cacheable Content | Informational | 4 |
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks. Including (but not limited to) Cross Site Scripting (XSS), and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.
GET
Content-Security-Policy
default-src 'none'
GET
Content-Security-Policy
default-src 'none'
GET
Content-Security-Policy
default-src 'none'
GET
Content-Security-Policy
default-src 'none'
GET
Content-Security-Policy
default-src 'none'
GET
Content-Security-Policy
default-src 'none'
Instances: 6
Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.
GET
Instances: 1
Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.
The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against 'ClickJacking' attacks.
GET
x-frame-options
Instances: 1
Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app. If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.
Permissions Policy Header is an added layer of security that helps to restrict from unauthorized access or usage of browser/client features by web resources. This policy ensures the user privacy by limiting or specifying the features of the browsers can be used by the web resources. Permissions Policy provides a set of standard HTTP headers that allow website owners to limit which features of browsers can be used by the page such as camera, microphone, location, full screen etc.
GET
GET
GET
GET
GET
GET
GET
Instances: 7
Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header.
The web/application server is leaking information via one or more "X-Powered-By" HTTP response headers. Access to such information may facilitate attackers identifying other frameworks/components your web application is reliant upon and the vulnerabilities such components may be subject to.
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
GET
X-Powered-By: Express
Instances: 10
Ensure that your web server, application server, load balancer, etc. is configured to suppress "X-Powered-By" headers.
HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797.
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
Instances: 10
Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.
The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.
GET
x-content-type-options
GET
x-content-type-options
GET
x-content-type-options
GET
x-content-type-options
Instances: 4
Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages. If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.
The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.
GET
user
Instances: 1
Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.
The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.
GET
<script>!function(e){function r(r){for(var a,o,c=r[0],d=r[1],u=r[2],b=0,l=[];b<c.length;b++)o=c[b],Object.prototype.hasOwnProperty.call(n,o)&&n[o]&&l.push(n[o][0]),n[o]=0;for(a in d)Object.prototype.hasOwnProperty.call(d,a)&&(e[a]=d[a]);for(i&&i(r);l.length;)l.shift()();return f.push.apply(f,u||[]),t()}function t(){for(var e,r=0;r<f.length;r++){for(var t=f[r],a=!0,c=1;c<t.length;c++){var d=t[c];0!==n[d]&&(a=!1)}a&&(f.splice(r--,1),e=o(o.s=t[0]))}return e}var a={},n={15:0},f=[];function o(r){if(a[r])return a[r].exports;var t=a[r]={i:r,l:!1,exports:{}};return e[r].call(t.exports,t,t.exports,o),t.l=!0,t.exports}o.e=function(e){var r,t=[],a=n[e];if(0!==a)if(a)t.push(a[2]);else{var f=new Promise((function(r,t){a=n[e]=[r,t]}));t.push(a[2]=f);var c,d=document.createElement("script");d.charset="utf-8",d.timeout=120,o.nc&&d.setAttribute("nonce",o.nc),d.src=(r=e,o.p+"static/js/"+({}[r]||r)+"."+{0:"effd86d6",1:"4d3b42e0",2:"ab982430",3:"3da244e3",4:"7e2af864",5:"edd6d6ae",6:"095c08eb",7:"c89d0a43",8:"33f0a955",9:"ee96bd8a",10:"0952653f",11:"4d10f257",12:"e7740bb4",13:"2ed9069b",17:"fbd79dd7",18:"282814ac",19:"913854f0",20:"e995ff38",21:"e5e47065",22:"47e18bf8",23:"0b344191",24:"563496ce",25:"e214af76",26:"b358e03b",27:"e509296f",28:"aea282d0",29:"d62c9ca0",30:"a9203a76",31:"3fe601bf",32:"f9542e7f",33:"e638323e",34:"d170995a",35:"de5c66e6",36:"20a5fedb",37:"c145ddab",38:"cd1cd454",39:"0ed2f18d",40:"b91fd6bb",41:"fec0ebd3",42:"8e8e282a",43:"40902317",44:"cac49052",45:"fa693a06",46:"d6edb097",47:"62e04a11",48:"f135f583",49:"7b384679",50:"1e793b78",51:"347adf89",52:"bfcb2860",53:"4afac4f3",54:"e597c1f9",55:"c307a9d1",56:"1560b23a",57:"48b905d0",58:"f98645a2",59:"97709d41",60:"2ecd0b3f",61:"9dff62f3",62:"a40011d3",63:"676258f0",64:"60f0b23f",65:"bdc702b4",66:"01fbdc37",67:"53fe201a",68:"b1e4ccd8",69:"5fe88d9f",70:"e76f27e0",71:"d26b0401",72:"020d98bb",73:"487cd5df",74:"8c864735",75:"0ea4700c",76:"53e5204f",77:"f02ea728",78:"6c0092a8",79:"5a33af59",80:"f61315cb",81:"dd94511c",82:"b6a514f3",83:"9b24ce08",84:"0fe533a5"}[r]+".chunk.js");var u=new Error;c=function(r){d.onerror=d.onload=null,clearTimeout(i);var t=n[e];if(0!==t){if(t){var a=r&&("load"===r.type?"missing":r.type),f=r&&r.target&&r.target.src;u.message="Loading chunk "+e+" failed.\n("+a+": "+f+")",u.name="ChunkLoadError",u.type=a,u.request=f,t[1](u)}n[e]=void 0}};var i=setTimeout((function(){c({type:"timeout",target:d})}),12e4);d.onerror=d.onload=c,document.head.appendChild(d)}return Promise.all(t)},o.m=e,o.c=a,o.d=function(e,r,t){o.o(e,r)||Object.defineProperty(e,r,{enumerable:!0,get:t})},o.r=function(e){"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},o.t=function(e,r){if(1&r&&(e=o(e)),8&r||4&r&&"object"==typeof e&&e&&e.__esModule)return e;var t=Object.create(null);if(o.r(t),Object.defineProperty(t,"default",{enumerable:!0,value:e}),2&r&&"string"!=typeof e)for(var a in e)o.d(t,a,function(r){return e[r]}.bind(null,a));return t},o.n=function(e){var r=e&&e.__esModule?function(){return e.default}:function(){return e};return o.d(r,"a",r),r},o.o=function(e,r){return Object.prototype.hasOwnProperty.call(e,r)},o.p="/",o.oe=function(e){throw console.error(e),e};var c=this["webpackJsonpixcs-portal-user"]=this["webpackJsonpixcs-portal-user"]||[],d=c.push.bind(c);c.push=r,c=c.slice();for(var u=0;u<c.length;u++)r(c[u]);var i=d;t()}([])</script>
Instances: 1
This is an informational alert and so no changes are required.
The cache-control header has not been set properly or is missing, allowing the browser and proxies to cache content. For static assets like css, js, or image files this might be intended, however, the resources should be reviewed to ensure that no sensitive content will be cached.
GET
cache-control
public, max-age=0
GET
cache-control
public, max-age=0
GET
cache-control
public, max-age=0
Instances: 3
For secure content, ensure the cache-control HTTP header is set with "no-cache, no-store, must-revalidate". If an asset should be cached consider setting the directives "public, max-age, immutable".
Specifies how and where the data would be used. For instance, if the value is audio, then the requested resource must be audio data and not any other type of resource.
GET
Sec-Fetch-Dest
GET
Sec-Fetch-Dest
GET
Sec-Fetch-Dest
Instances: 3
Ensure that Sec-Fetch-Dest header is included in request headers.
Allows to differentiate between requests for navigating between HTML pages and requests for loading resources like images, audio etc.
GET
Sec-Fetch-Mode
GET
Sec-Fetch-Mode
GET
Sec-Fetch-Mode
Instances: 3
Ensure that Sec-Fetch-Mode header is included in request headers.
Specifies the relationship between request initiator's origin and target's origin.
GET
Sec-Fetch-Site
GET
Sec-Fetch-Site
GET
Sec-Fetch-Site
Instances: 3
Ensure that Sec-Fetch-Site header is included in request headers.
Specifies if a navigation request was initiated by a user.
GET
Sec-Fetch-User
GET
Sec-Fetch-User
GET
Sec-Fetch-User
Instances: 3
Ensure that Sec-Fetch-User header is included in user initiated requests.
The response contents are storable by caching components such as proxy servers, and may be retrieved directly from the cache, rather than from the origin server by the caching servers, in response to similar requests from other users. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where "shared" caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.
GET
GET
GET
GET
GET
GET
Instances: 6
Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user: Cache-Control: no-cache, no-store, must-revalidate, private Pragma: no-cache Expires: 0 This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.
The response contents are storable by caching components such as proxy servers, but will not be retrieved directly from the cache, without validating the request upstream, in response to similar requests from other users.
GET
max-age=0
GET
max-age=0
GET
max-age=0
GET
max-age=0
Instances: 4
View the following link to download the report. RunnerID:5794722307