Vulnerability Scan Result


Title: | Personal Finance Forecasting | Nova Money |
Description: | Nova Money is a personal finance app that forecasts your cash flows and predict when you need to slowdown your spending, so you can strike a balance between enjoying life today and growing your future net worth. The Nova AI uses Open Banking data to plan months ahead without spreadsheets. |
ip_address | 3.75.10.80 |
country | DE ![]() |
network_name | Amazon Inc |
asn | AS16509 |
ip_address | 3.124.100.143 |
country | DE ![]() |
network_name | Amazon Inc |
asn | AS16509 |
80/tcp | http | Netlify - |
443/tcp | https | Netlify - |
Software / Version | Category |
---|---|
Google Hosted Libraries | CDN |
Emotion | JavaScript frameworks, Development |
Google Font API | Font scripts |
HTTP/3 | Miscellaneous |
jQuery 3.5.1 | JavaScript libraries |
MobX | JavaScript libraries |
Open Graph | Miscellaneous |
React | JavaScript frameworks |
Segment 4.15.3 | Customer data platform |
Unpkg | CDN |
Webflow 1.6.0 | Page builders |
Webpack | Miscellaneous |
Cloudflare | CDN |
Netlify | PaaS, CDN |
HSTS | Security |
Web Application Vulnerabilities
Evidence
URL | Evidence |
---|---|
https://novamoney.com/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
CWE | CWE-693 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
URL | Evidence |
---|---|
https://novamoney.com/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options
header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
CWE | CWE-693 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
URL | Evidence |
---|---|
https://novamoney.com/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy
HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
CWE | CWE-693 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
URL | Method | Parameters | Evidence |
---|---|---|---|
https://novamoney.com/usecase | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 |
|
Vulnerability description
We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Risk description
The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.
Recommendation
Ensure that all external resources the page references are loaded using HTTPS.
Classification
CWE | CWE-311 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
Software / Version | Category |
---|---|
Google Hosted Libraries | CDN |
Emotion | JavaScript frameworks, Development |
Google Font API | Font scripts |
HTTP/3 | Miscellaneous |
jQuery 3.5.1 | JavaScript libraries |
MobX | JavaScript libraries |
Open Graph | Miscellaneous |
React | JavaScript frameworks |
Segment 4.15.3 | Customer data platform |
Unpkg | CDN |
Webflow 1.6.0 | Page builders |
Webpack | Miscellaneous |
Cloudflare | CDN |
Netlify | PaaS, CDN |
HSTS | Security |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
Vulnerability description
Website is accessible.
Evidence
URL | Method | Parameters | Evidence |
---|---|---|---|
https://novamoney.com/terms | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Email Address: hello@novamoney.com |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
CWE | CWE-200 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
novamoney.com | SPF | Sender Policy Framework | "v=spf1 include:spf.sendinblue.com include:_spf.firebasemail.com ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
_dmarc.novamoney.com | TXT | Text record | "v=DMARC1; p=reject; pct=1; ri=86400; sp=none; rua=mailto:vkx4mw9h@ag.eu.dmarcian.com, mailto:dmarc@mailinblue.com!10m; ruf=mailto:vkx4mw9h@fr.eu.dmarcian.com; rf=afrf;" |
Vulnerability description
We found that the DMARC record for the domain is configured with sp=none, meaning that no policy is enforced for subdomains. This allows subdomains to send emails without being subject to DMARC checks, making it easier for attackers to spoof emails from these subdomains. Subdomains are often overlooked in email security, and attackers can exploit this misconfiguration to launch phishing or spoofing attacks from seemingly legitimate subdomains of a protected domain.
Risk description
When the DMARC record is configured with sp=none, subdomains are not subject to DMARC enforcement, allowing attackers to spoof emails from subdomains without being blocked. This creates a significant risk of phishing and impersonation attacks, where malicious emails appear to originate from trusted subdomains. These spoofed emails can be used to deceive users or damage the organization's reputation, undermining the security benefits of DMARC for the primary domain.
Recommendation
To mitigate the risk, we recommend that the subdomain policy should be updated to sp=reject to ensure that any email failing DMARC checks from subdomains is automatically rejected. This will help prevent unauthorized emails from being sent from subdomains, reducing the risk of spoofing and phishing. Additionally, it's important to regularly monitor DMARC reports to track email activity from subdomains and adjust policies as needed to maintain consistent security across the entire domain.
Evidence
DKIM selector | Key type | Key size | Value |
---|---|---|---|
rsa | 1296 | "k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
novamoney.com | A | IPv4 address | 3.124.100.143 |
novamoney.com | A | IPv4 address | 3.75.10.80 |
novamoney.com | NS | Name server | amy.ns.cloudflare.com |
novamoney.com | NS | Name server | rudy.ns.cloudflare.com |
novamoney.com | MX | Mail server | 1 aspmx.l.google.com |
novamoney.com | MX | Mail server | 10 alt3.aspmx.l.google.com |
novamoney.com | MX | Mail server | 10 alt4.aspmx.l.google.com |
novamoney.com | MX | Mail server | 5 alt1.aspmx.l.google.com |
novamoney.com | MX | Mail server | 5 alt2.aspmx.l.google.com |
novamoney.com | SOA | Start of Authority | amy.ns.cloudflare.com. dns.cloudflare.com. 2374728221 10000 2400 604800 1800 |
novamoney.com | AAAA | IPv6 address | 2a05:d014:58f:6200::65 |
novamoney.com | AAAA | IPv6 address | 2a05:d014:58f:6202::65 |
novamoney.com | TXT | Text record | "Sendinblue-code:feb1e7e54dc2f4484dfea90ac7c0db3d" |
novamoney.com | TXT | Text record | "facebook-domain-verification=kuw7lpf58b8y4t26vwbomeh1bmxdyu" |
novamoney.com | TXT | Text record | "firebase=cashcoach" |
novamoney.com | TXT | Text record | "google-site-verification=mW7Wnp1-UBdw4VNqqBG2RkFW87XQqgy4BDcVm4Ffsqc" |
novamoney.com | TXT | Text record | "google-site-verification=seKGWFCZIlAueGPEWkea9pu09f6xWm7qgzQGnI_WwqM" |
novamoney.com | TXT | Text record | "proxy-ssl.webflow.com" |
novamoney.com | SPF | Sender Policy Framework | "v=spf1 include:spf.sendinblue.com include:_spf.firebasemail.com ~all" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
novamoney.com | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
_dmarc.novamoney.com | TXT | Text record | "v=DMARC1; p=reject; pct=1; ri=86400; sp=none; rua=mailto:vkx4mw9h@ag.eu.dmarcian.com, mailto:dmarc@mailinblue.com!10m; ruf=mailto:vkx4mw9h@fr.eu.dmarcian.com; rf=afrf;" |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.
Evidence
Vulnerability description
OS detection couldn't determine the operating system.
Evidence
We managed to detect the redirect using the following Request / Response chain.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.
Evidence
DKIM selector | Key type | Key size | Value |
---|---|---|---|
rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0eymNXvYYR6d9clwZFuLY4k7f3kIFzQCmtUHOEtgN/Jqs1xAyRgo1jHQi4Ta2YH/uez31ItMT4Nn7AoXbJ5dauezd42D29ufJFgevcYcsVZ/HIQi/Tj2chJgZb9R/fVFtqj/pHLD9BHFJ7G5BkcA2eLu5N9T/8mYLFqppO06T8nsj3cYdJldEz88bAJGBFJGM" "UTfEoUayihipzk2rqiQhOpfgg0NDUAMdRLX1Bi5Er3IfxMyEOtRWP6FpQnBTR0JUYT2vxbhtE7famLyT5mv38JmpumOKRFsMhMaCIVlIQbTClQ7tbruomwlnC9qyiz7INH4YbJI3wTopMhPIBdBKQIDAQAB" | |
rsa | 1296 | "k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB" | |
s1 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArXtbTfZDuQF2hDDNCthec0ONCAdYmztlv+a3t35FVPLZDMXWrMvpMtidw05Dn2yeY3Cl0IOfjeOEcMg5mA2Wi9E9+NGSZvpElB2rQsZtc6QniANExJmFKPprVB2Mps8YFnkoWEPulZLPq39tLQj6bcoWzT72U4EN/5PlESRY3E2+iDp5kYouYB3K3Aqaw0ffnHifu" "S+/djUEcjnDT2t7hvw+T15S52Q0HarDfgjEkR1pgDohAVtT0fUeWYQvGjReTbhp6OdRYYrS4lYeRAptYxXfZj37gwJgPBwXCkJCdMtoIy52MXnkTdcFoVbpVUfXtU+nbEhNmMp0QF3MNuUUaQIDAQAB" |
s2 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqv1x7yzbWf1lxl56wLkyKPOlJdAlATHvnYVsGvL+VaRiyMnPrBit+u10WU4Ro9JQThU3IQknooAHJBw8y75wXmW5ZO8XG/+iDL//Wzi/7YwIgkGZyePDJflbNudMcF2gKKBNqD+Xdh2T7/e0rtiS+ZjNXeagMR+AIl12rjK5Ug1F4MZcRl1xJ6OL0oS811OM18fiz" "2RngGQOiMqVjSjwA7uNPcRe24ruOPCV9tCm2G04le6fUYmzQc6MSp/3GLj++j/MfHd62BsFDoyRk+TEkD1wbUmnA7h6mzv05SZW3EIXdqfAvSOGa9/7EcwMXAbK0jKtpqvvF0tuDBLB7Ox2EQIDAQAB" |
Evidence
Software / Version | Category |
---|---|
Webflow | Page builders |
Segment | Customer data platform |
jQuery 3.5.1 | JavaScript libraries |
Google Hosted Libraries | CDN |
Google Font API | Font scripts |
Netlify | PaaS, CDN |
HSTS | Security |
Cloudflare | CDN |
HTTP/3 | Miscellaneous |
Open Graph | Miscellaneous |
Unpkg | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.