Vulnerability Scan Result

ip_address | 12.110.193.205 |
country | US ![]() |
network_name | AT&T Services Inc |
asn | AS7018 |
80/tcp | http | Microsoft HTTPAPI httpd 2 |
443/tcp | https | Microsoft IIS httpd 7.5 |
Software / Version | Category |
---|---|
Microsoft HTTPAPI 2.0 | Web servers |
Web Application Vulnerabilities
Evidence
URL | Response URL | Evidence |
---|---|---|
http://dev.accunet.accutechdata.com/ | http://dev.accunet.accutechdata.com/ | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
CWE | CWE-311 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
Software / Version | Category |
---|---|
Microsoft HTTPAPI 2.0 | Web servers |
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.
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
CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
---|---|---|---|---|---|
CVE-2010-3972 | 10 | 0.91689 | 0.99658 | No | Heap-based buffer overflow in the TELNET_STREAM_CONTEXT::OnSendData function in ftpsvc.dll in Microsoft FTP Service 7.0 and 7.5 for Internet Information Services (IIS) 7.0, and IIS 7.5, allows remote attackers to execute arbitrary code or cause a denial of service (daemon crash) via a crafted FTP command, aka "IIS FTP Service Heap Buffer Overrun Vulnerability." NOTE: some of these details are obtained from third party information. |
CVE-2010-2730 | 9.3 | 0.10296 | 0.92813 | No | Buffer overflow in Microsoft Internet Information Services (IIS) 7.5, when FastCGI is enabled, allows remote attackers to execute arbitrary code via crafted headers in a request, aka "Request Header Buffer Overflow Vulnerability." |
CVE-2010-1899 | 4.3 | 0.87011 | 0.99392 | No | Stack consumption vulnerability in the ASP implementation in Microsoft Internet Information Services (IIS) 5.1, 6.0, 7.0, and 7.5 allows remote attackers to cause a denial of service (daemon outage) via a crafted request, related to asp.dll, aka "IIS Repeated Parameter Request Denial of Service Vulnerability." |
Vulnerability description
Vulnerabilities found for IIS 7.5
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
CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
---|---|---|---|---|---|
CVE-2024-21490 | 7.5 | 0.0062 | 0.69108 | No | This affects versions of the package angular from 1.3.0. A regular expression used to split the value of the ng-srcset directive is vulnerable to super-linear runtime due to backtracking. With large carefully-crafted input, this can result in catastrophic backtracking and cause a denial of service. **Note:** This package is EOL and will not receive any updates to address this issue. Users should migrate to [@angular/core](https://www.npmjs.com/package/@angular/core). |
CVE-2019-10768 | 5 | 0.0042 | 0.61111 | No | In AngularJS before 1.7.9 the function `merge()` could be tricked into adding or modifying properties of `Object.prototype` using a `__proto__` payload. |
CVE-2024-8373 | 4.8 | 0.0004 | 0.11448 | No | Improper sanitization of the value of the [srcset] attribute in <source> HTML elements in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing . This issue affects all versions of AngularJS. Note: The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see here https://docs.angularjs.org/misc/version-support-status . |
CVE-2024-8372 | 4.8 | 0.00139 | 0.34751 | No | Improper sanitization of the value of the 'srcset' attribute in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing . This issue affects AngularJS versions 1.3.0-rc.4 and greater. Note: The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see here https://docs.angularjs.org/misc/version-support-status . |
CVE-2020-7676 | 3.5 | 0.00753 | 0.72239 | No | angular.js prior to 1.8.0 allows cross site scripting. The regex-based input HTML replacement may turn sanitized code into unsanitized one. Wrapping "<option>" elements in "<select>" ones changes parsing behavior, leading to possibly unsanitizing code. |
Vulnerability description
Vulnerabilities found for AngularJS 1.6.4
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
CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
---|---|---|---|---|---|
CVE-2020-28458 | 7.5 | 0.00957 | 0.75472 | No | All versions of package datatables.net are vulnerable to Prototype Pollution due to an incomplete fix for https://snyk.io/vuln/SNYK-JS-DATATABLESNET-598806. |
CVE-2021-23445 | 4.3 | 0.00461 | 0.63249 | No | This affects the package datatables.net before 1.11.3. If an array is passed to the HTML escape entities function it would not have its contents escaped. |
Vulnerability description
Vulnerabilities found for DataTables 1.10.21
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
CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
---|---|---|---|---|---|
CVE-2024-6484 | 6.4 | 0.00044 | 0.13052 | No | A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an <a> tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser. |
CVE-2018-20676 | 4.3 | 0.06255 | 0.90457 | No | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. |
CVE-2018-14042 | 4.3 | 0.017 | 0.8149 | No | In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. |
CVE-2018-14040 | 4.3 | 0.01633 | 0.81103 | No | In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute. |
CVE-2016-10735 | 4.3 | 0.06152 | 0.90377 | No | In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041. |
Vulnerability description
Vulnerabilities found for Bootstrap 3.3.7
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
CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
---|---|---|---|---|---|
CVE-2020-11023 | 4.3 | 0.21757 | 0.95461 | Yes | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
CVE-2020-11022 | 4.3 | 0.23711 | 0.95733 | No | In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
CVE-2019-11358 | 4.3 | 0.02777 | 0.85438 | No | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
Vulnerability description
Vulnerabilities found for jQuery 3.2.1
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
CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
---|---|---|---|---|---|
CVE-2022-31160 | 6.1 | 0.06584 | 0.90713 | No | jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`. |
CVE-2021-41184 | 4.3 | 0.2794 | 0.96238 | No | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources. |
CVE-2021-41183 | 4.3 | 0.01538 | 0.8053 | No | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML. A workaround is to not accept the value of the `*Text` options from untrusted sources. |
CVE-2021-41182 | 4.3 | 0.1926 | 0.95066 | No | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources. |
Vulnerability description
Vulnerabilities found for jQuery UI 1.12.1
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 managed to detect that AngularJS has reached the End-of-Life (EOL).
Version detected: 1.6.4 End-of-life date: 2021-12-31 Latest version for the cycle: 1.6.10 This release cycle (1.6) doesn't have long-term-support (LTS). The cycle was released on 2016-12-08 and its latest release date was 2018-04-17.
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
We managed to detect that Bootstrap has reached the End-of-Life (EOL).
Version detected: 3.3.7 End-of-life date: 2019-07-24 Latest version for the cycle: 3.4.1 This release cycle (3) does have long-term-support (LTS). The cycle was released on 2013-08-19 and its latest release date was 2019-02-13. The support ended on 2016-09-05.
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
Software / Version | Category |
---|---|
Microsoft HTTPAPI 2.0 | Web servers |
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 |
---|---|
Microsoft Windows Vista SP0 or SP1, Windows Server 2008 SP1, or Windows 7 | 100% |
Vulnerability description
OS Detection
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
dev.accunet.accutechdata.com | A | IPv4 address | 12.110.193.205 |
dev.accunet.accutechdata.com | MX | Mail server | 10 accutechdata-com.mail.protection.outlook.com |
dev.accunet.accutechdata.com | SOA | Start of Authority | ns71.domaincontrol.com. dns.jomax.net. 2024121002 28800 7200 604800 3600 |
dev.accunet.accutechdata.com | TXT | Text record | "google-site-verification=1TlYg1KNL48rHhIFv-7hdrq0BgmUwzF0gU4xbg7GmHs" |
dev.accunet.accutechdata.com | TXT | Text record | "ppe-cf2d14912bbe472f367e" |
dev.accunet.accutechdata.com | TXT | Text record | "rj1g1BLbyTBhZ/sEBhFptrNviQldy62cpmIp/aIcoe7fSEI0vty8xyl5ycV3CdJGCNJRTRys/Z+yaVfGweOOkQ==" |
dev.accunet.accutechdata.com | TXT | Text record | "v=DMARC1;p=quarantine;pct=100" |
dev.accunet.accutechdata.com | TXT | Text record | "mandrill_verify.ZmmfPp9fpMSp2QCfk8X5yg" |
dev.accunet.accutechdata.com | SPF | Sender Policy Framework | "v=spf1 mx ip4:199.187.243.163 ip4:72.29.168.192/27 ip4:96.89.58.121 a:outbound-us1.ppe-hosted.com a:dispatch-us.ppe-hosted.com include:servers.mcsv.net include:_spf.psm.knowbe4.com include:spf.protection.outlook.com include:helpscoutemail.com include:help" "scout.net ~all" |
dev.accunet.accutechdata.com | CNAME | Canonical name | dev.accunet.accutechdata.com.cdn.cloudflare.net |
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 |
---|---|
Windows Server | Operating systems |
Bootstrap 3.3.7 | UI frameworks |
Microsoft ASP.NET 4.0.30319 | Web frameworks |
AngularJS 1.6.4 | JavaScript frameworks |
IIS 7.5 | Web servers |
Google Ads | Advertising |
Cloudflare | CDN |
pdfmake | JavaScript libraries |
OWL Carousel | JavaScript libraries |
jQuery CDN | CDN |
Google Hosted Libraries | CDN |
Google Ads Conversion Tracking | Analytics |
cdnjs | CDN |
Modernizr 2.8.3 | JavaScript libraries |
jQuery UI 1.12.1 | JavaScript libraries |
jQuery Migrate 3.0.0 | JavaScript libraries |
jQuery 3.2.1 | JavaScript libraries |
Google Tag Manager | Tag managers |
Google Analytics UA | Analytics |
DataTables 1.10.21 | JavaScript libraries |
core-js 2.4.0 | JavaScript libraries |
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.