Vulnerability Scan Result
| Title: | Home - Burke Middle College |
| Description: | Home - Burke Middle College |
| ip_address | 104.17.166.123 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.17.164.123 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.17.165.123 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.17.162.123 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.17.163.123 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | Cloudflare http proxy - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | https | Cloudflare http proxy - |
| Software / Version | Category |
|---|---|
| Adobe ColdFusion | Web frameworks |
| cdnjs | CDN |
| CodeMirror 4.7.0 | Editors |
| Firebase 9.14.0 | Databases, Development |
| libphonenumber | JavaScript libraries |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| Web Font Loader | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| Java | Programming languages |
| jQuery 3.5.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| Open Graph | Miscellaneous |
| Selectize | JavaScript libraries |
| Algolia | Search engines |
| Microsoft ASP.NET | Web frameworks |
| Cloudflare | CDN |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| JSP | Web frameworks |
| Weglot | Translation |
Web Application Vulnerabilities
Evidence
| Risk Level | CVSS | CVE | Summary | Affected software |
|---|---|---|---|---|
| 5 | CVE-2020-7760 | This affects the package codemirror before 5.58.2; the package org.apache.marmotta.webjars:codemirror before 5.58.2. The vulnerable regular expression is located in https://github.com/codemirror/CodeMirror/blob/cdb228ac736369c685865b122b736cd0d397836c/mode/javascript/javascript.jsL129. The ReDOS vulnerability of the regex is mainly due to the sub-pattern (s|/*.*?*/)* | codemirror 4.7.0 |
Vulnerability description
We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.
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-1026 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://bmc.burke.k12.nc.us/ | __cfruid | Set-Cookie: .bmc.burke.k12.nc.us |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://bmc.burke.k12.nc.us/ | 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
| Software / Version | Category |
|---|---|
| Adobe ColdFusion | Web frameworks |
| cdnjs | CDN |
| CodeMirror 4.7.0 | Editors |
| Firebase 9.14.0 | Databases, Development |
| libphonenumber | JavaScript libraries |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| Web Font Loader | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| Java | Programming languages |
| jQuery 3.5.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Lightbox | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| Open Graph | Miscellaneous |
| Selectize | JavaScript libraries |
| Algolia | Search engines |
| Microsoft ASP.NET | Web frameworks |
| Cloudflare | CDN |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| JSP | Web frameworks |
| Weglot | Translation |
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
We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.
Risk description
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).
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.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | 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 |
|---|---|
| FreeBSD 11.0-RELEASE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Algolia | Search engines |
| Ruby | Programming languages |
| Java | Programming languages |
| CFML | Programming languages |
| JSP | Web frameworks |
| Ruby on Rails | Web frameworks |
| Adobe ColdFusion | Web frameworks |
| Microsoft ASP.NET | Web frameworks |
| Weglot | Translation |
| Web Font Loader | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| cdnjs | CDN |
| Cloudflare Browser Insights | Analytics, RUM |
| reCAPTCHA | Security |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| bmc.burke.k12.nc.us | A | IPv4 address | 104.17.163.123 |
| bmc.burke.k12.nc.us | A | IPv4 address | 104.17.165.123 |
| bmc.burke.k12.nc.us | A | IPv4 address | 104.17.162.123 |
| bmc.burke.k12.nc.us | A | IPv4 address | 104.17.164.123 |
| bmc.burke.k12.nc.us | A | IPv4 address | 104.17.166.123 |
| bmc.burke.k12.nc.us | AAAA | IPv6 address | 2606:4700::6811:a27b |
| bmc.burke.k12.nc.us | AAAA | IPv6 address | 2606:4700::6811:a57b |
| bmc.burke.k12.nc.us | AAAA | IPv6 address | 2606:4700::6811:a37b |
| bmc.burke.k12.nc.us | AAAA | IPv6 address | 2606:4700::6811:a67b |
| bmc.burke.k12.nc.us | AAAA | IPv6 address | 2606:4700::6811:a47b |
| bmc.burke.k12.nc.us | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| bmc.burke.k12.nc.us | CAA | Certificate Authority Authorization | 0 issue "digicert.com" |
| bmc.burke.k12.nc.us | CAA | Certificate Authority Authorization | 0 issue "godaddy.com" |
| bmc.burke.k12.nc.us | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| bmc.burke.k12.nc.us | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| bmc.burke.k12.nc.us | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| bmc.burke.k12.nc.us | CNAME | Canonical name | burkek12ncus.finalsite.com |
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 |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Software / Version | Category |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | 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.