Vulnerability Scan Result
| Title: | NobleBlocks |
| Description: | A decentralized platform for scientific publications. Making scientific publishing accessible and rewarding with NobleBlocks' blockchain-powered platform |
| ip_address | 195.5.171.242 |
| country | US  |
| network_name | DFINITY USA Research, LLC |
| asn | AS398485 |
| ip_address | 212.71.124.188 |
| country | CH  |
| network_name | EveryWare AG |
| asn | AS24951 |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Next.js 13.3.0 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Webpack | Miscellaneous |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2025-29927 | 9.1 | 0.99621 | 0.99946 | Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3. |
| CVE-2026-44573 | 7.5 | 0.00457 | 0.36461 | Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2025-67779 | 7.5 | 0.1888 | 0.96943 | It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case. React Server Components versions 19.0.2, 19.1.3 and 19.2.2 are affected, allowing unsafe deserialization of payloads from HTTP requests to Server Function endpoints. This can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served. |
| CVE-2025-55184 | 7.5 | 0.65592 | 0.99167 | A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints, which can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served. |
| CVE-2024-51479 | 7.5 | 0.03884 | 0.88937 | Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] `https://example.com/` * [Affected] `https://example.com/foo` * [Not affected] `https://example.com/foo/bar`. This issue is patched in Next.js `14.2.15` and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Next.js 13.3.0 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Webpack | Miscellaneous |
| 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://rltrx-laaaa-aaaai-qpabq-cai.icp0.io/components/Benefits.html | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2025-29927 | 9.1 | 0.99621 | 0.99946 | No | Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3. |
| CVE-2026-44573 | 7.5 | 0.00457 | 0.36461 | No | Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5. |
| CVE-2025-67779 | 7.5 | 0.1888 | 0.96943 | No | It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case. React Server Components versions 19.0.2, 19.1.3 and 19.2.2 are affected, allowing unsafe deserialization of payloads from HTTP requests to Server Function endpoints. This can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served. |
| CVE-2025-55184 | 7.5 | 0.65592 | 0.99167 | No | A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints, which can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served. |
| CVE-2024-51479 | 7.5 | 0.03884 | 0.88937 | No | Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] `https://example.com/` * [Affected] `https://example.com/foo` * [Not affected] `https://example.com/foo/bar`. This issue is patched in Next.js `14.2.15` and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability. |
Vulnerability description
Vulnerabilities found for Next.js 13.3.0
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed "high" severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We found insecure DNS cookie usage on the following nameservers: hassan.ns.cloudflare.com, lara.ns.cloudflare.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
We managed to detect that Next.js has reached the End-of-Life (EOL).
Version detected: 13.3.0 End-of-life date: 2024-12-21 Latest version for the cycle: 13.5.11 This release cycle (13) doesn't have long-term-support (LTS). The cycle was released on 2022-10-25 and its latest release date was 2025-03-27.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | A | IPv4 address | 212.71.124.188 |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | A | IPv4 address | 195.5.171.242 |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | NS | Name server | hassan.ns.cloudflare.com |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | NS | Name server | lara.ns.cloudflare.com |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 ch1-bnp00-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 dm1-bnp00-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 fr1-bnp01-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 se1-bnp00-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 sin1-bnp02-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 tp1-bnp02-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 tyo1-bnp02-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | MX | Mail server | 10 zh2-bnp04-vm.ic0.app |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | SOA | Start of Authority | hassan.ns.cloudflare.com. dns.cloudflare.com. 2407908942 10000 2400 604800 1800 |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | AAAA | IPv6 address | 2602:fb2b:110:1:bcfb:b8ff:fe09:c741 |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:61ff:fe45:43ab |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| rltrx-laaaa-aaaai-qpabq-cai.icp0.io | CNAME | Canonical name | boundary.dfinity.network |
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
| Software / Version | Category |
|---|---|
| Next.js 13.3.0 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| React | JavaScript frameworks |
| Font Awesome | Font scripts |
| HSTS | Security |
| Webpack | Miscellaneous |
| Open Graph | Miscellaneous |
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
| Operating System | Accuracy |
|---|---|
| Linux 3.4 | 89% |
Vulnerability description
OS Detection