Misconfigured Content Security Policy

Kindly assist to resolve the below vulnerability

Description:  A misconfigured Content Security Policy (CSP) can expose a web application to various security vulnerabilities, compromising the integrity, confidentiality, and availability of the application and its data. The misconfiguration can occur due to overly permissive settings, the use of insecure directives, or a lack of specificity in defining resource sources.

Impact: The presence of unsafe-inline in the Content Security Policy (CSP) does not have an immediate impact if no inline scripts are used or executed. Unsafe-eval is also present which allows the use of JavaScript’s eval() function and similar methods (e.g., setTimeout() with string arguments) However, it weakens the overall security posture by allowing potential future 

It is recommended to Remove unsafe-inline and Remove unsafe-eval


here is CSF currently using
aReply.AddHeader('Content-Security-Policy', 'default-src https: ' + quotedstr('self') +
    '; img-src https: ' + quotedstr('self') +
    '; object-src https: ' + quotedstr('self') +
    '; style-src https: ' +  quotedstr('self')+
    ' '+ quotedstr('unsafe-inline') +
    '; script-src https: ' + quotedstr('self')+
    ' '+ quotedstr('unsafe-inline') +
    ' '+  quotedstr('unsafe-eval') +
    '; frame-ancestors ' + QuotedStr('self'));

Remove the unsafe-inline and unsafe-eval will meet the purpose?