Vulnerability Scan Result
| Title: | TreeGAN: Syntax-Aware Sequence Generation with Generative Adversarial Networks | IEEE Conference Publication | IEEE Xplore |
| Description: | No description found |
| ip_address | 18.66.195.79 |
| country | US  |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 18.66.195.114 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 18.66.195.59 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 18.66.195.11 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | CloudFront - |
| Software / Version | Category |
|---|---|
| Angular 16.2.12 | JavaScript frameworks |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Google Publisher Tag | Advertising |
| Adobe Experience Platform Launch | Tag managers |
| FingerprintJS 2 | JavaScript libraries, Browser fingerprinting |
| Adobe Client Data Layer 2.0.2 | JavaScript frameworks |
| Zone.js | JavaScript frameworks |
| core-js 3.45.0 | JavaScript libraries |
| Java | Programming languages |
| jQuery 3.5.1 | JavaScript libraries |
| lit-html 2.7.5 | JavaScript libraries |
| Modernizr | JavaScript libraries |
| Open Graph | Miscellaneous |
| Pure CSS | UI frameworks |
| Tealium | Tag managers, Customer data platform |
| Adobe Analytics | Analytics |
| FusionCharts | JavaScript graphics |
| GetFeedback | Issue trackers |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Lodash 3.10.1 | JavaScript libraries |
| MathJax 274 | JavaScript graphics |
| Osano | Cookie compliance |
| HSTS | Security |
| ServiceNow | Miscellaneous |
| JSP | Web frameworks |
| TypeScript | Programming languages |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2019-10744 | 9.1 | 0.0341 | 0.86979 | Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload. |
| CVE-2020-8203 | 7.4 | 0.02439 | 0.84547 | Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. |
| CVE-2021-23337 | 7.2 | 0.00493 | 0.6465 | Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. |
| CVE-2019-1010266 | 6.5 | 0.00196 | 0.419 | lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. |
| CVE-2018-3721 | 6.5 | 0.00187 | 0.40824 | lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects. |
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
| URL | Cookie Name | Evidence |
|---|---|---|
| https://ieeexplore.ieee.org/abstract/document/8594958 | AWSALBAPP-0, AWSALBAPP-1, AWSALBAPP-2, AWSALBAPP-3, TSaf720a17029 | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: AWSALBAPP-0=AAAAAAAAAADJmvqqNvJ1f3uvPrhxB/twiu4xo+7KRHnsCVaP2oqswOSfK/qbL9ps49xjamTewqv9rEBRnFlYWN1Lwd+Zae3/PYmN7MOskCcefrm24q2B3tr0gf+4CH1BHC09g8xEuYUNnzk/qNTgiWYD4pPvzJ4KdN7CKqh5Q4IyPKuJ7EFUoqcB+dNYIea4f20oLMoMnmNJEHvYQEGa8w== Set-Cookie: AWSALBAPP-1=remove Set-Cookie: AWSALBAPP-2=remove Set-Cookie: AWSALBAPP-3=remove Set-Cookie: TSaf720a17029=0807dc117eab28000f4c461bf61a13d5d8d018b90fa7fd3ff6cacd221dea73b4e996c330db1a9a3f7d01066f0b113a5b |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://ieeexplore.ieee.org/abstract/document/8594958 | TS016349ac | Set-Cookie: .ieeexplore.ieee.org |
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 | Cookie Name | Evidence |
|---|---|---|
| https://ieeexplore.ieee.org/abstract/document/8594958 | TSaf720a17029, TS8b476361027, TS016349ac | Set-Cookie: TSaf720a17029=0807dc117eab28000f4c461bf61a13d5d8d018b90fa7fd3ff6cacd221dea73b4e996c330db1a9a3f7d01066f0b113a5b Set-Cookie: TS8b476361027=0807dc117eab2000802b3724205e681e9d892c965d73f1eb4dd7c8d8be25f38b4a71a4e02c1cccd208c8c2a35411300025062ba575a0c9e1fec7ccd1d8bb1b5940eaa8f0caf3ba031bf0ef4b981132e45019da972f9872c356efde8c81042fae Set-Cookie: TS016349ac=01f15fc87cc18fad8d01879461178d9503fce6830f6b5dcd3617bf162e1167dde7d10029e96426159b934b53aa0d33061f83483c33 |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://ieeexplore.ieee.org/abstract/document/8594958 | 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://ieeexplore.ieee.org/abstract/document/8594958 | 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
| Software / Version | Category |
|---|---|
| Angular 16.2.12 | JavaScript frameworks |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Google Publisher Tag | Advertising |
| Adobe Experience Platform Launch | Tag managers |
| FingerprintJS 2 | JavaScript libraries, Browser fingerprinting |
| Adobe Client Data Layer 2.0.2 | JavaScript frameworks |
| Zone.js | JavaScript frameworks |
| core-js 3.45.0 | JavaScript libraries |
| Java | Programming languages |
| jQuery 3.5.1 | JavaScript libraries |
| lit-html 2.7.5 | JavaScript libraries |
| Modernizr | JavaScript libraries |
| Open Graph | Miscellaneous |
| Pure CSS | UI frameworks |
| Tealium | Tag managers, Customer data platform |
| Adobe Analytics | Analytics |
| FusionCharts | JavaScript graphics |
| GetFeedback | Issue trackers |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Lodash 3.10.1 | JavaScript libraries |
| MathJax 274 | JavaScript graphics |
| Osano | Cookie compliance |
| HSTS | Security |
| ServiceNow | Miscellaneous |
| JSP | Web frameworks |
| TypeScript | Programming languages |
| Cart Functionality | Ecommerce |
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://ieeexplore.ieee.org/abstract/document/8594958 | 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 | Operating system paths found in the HTTP response: |
Vulnerability description
We found operating system paths returned in a HTTP response.
Risk description
The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.
Recommendation
Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We found insecure EDNS configuration on the following nameservers: ns-1667.awsdns-16.co.uk ns-1667.awsdns-16.co.uk:
Vulnerability description
We found that the server does not properly implement EDNS (Extension Mechanisms for DNS). EDNS allows larger DNS packets and supports modern features such as DNSSEC.
Risk description
The risk exists because improper or missing EDNS support can lead to truncated responses, degraded DNS performance, and compatibility issues with DNSSEC. This exposes users to risks such as incomplete DNS resolution and failed DNSSEC validation.
Recommendation
We recommend ensuring the proper implementation of EDNS on the DNS server. Update the DNS server software to support EDNS fully, including modern features like DNSSEC. Regularly test DNS configurations to ensure compliance and performance.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-1293.awsdns-33.org, ns-147.awsdns-18.com, ns-1667.awsdns-16.co.uk, ns-782.awsdns-33.net
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
| Software / Version | Category |
|---|---|
| Java | Programming languages |
| MathJax 274 | JavaScript graphics |
| JSP | Web frameworks |
| Pure CSS | UI frameworks |
| Amazon Web Services | PaaS |
| reCAPTCHA | Security |
| HSTS | Security |
| Amazon CloudFront | CDN |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Osano | Cookie compliance |
| Modernizr | JavaScript libraries |
| jQuery 3.5.1 | JavaScript libraries |
| FingerprintJS 2 | JavaScript libraries, Browser fingerprinting |
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 |
|---|---|---|---|
| ieeexplore.ieee.org | A | IPv4 address | 18.66.195.59 |
| ieeexplore.ieee.org | A | IPv4 address | 18.66.195.79 |
| ieeexplore.ieee.org | A | IPv4 address | 18.66.195.11 |
| ieeexplore.ieee.org | A | IPv4 address | 18.66.195.114 |
| ieeexplore.ieee.org | NS | Name server | ns-1293.awsdns-33.org |
| ieeexplore.ieee.org | NS | Name server | ns-147.awsdns-18.com |
| ieeexplore.ieee.org | NS | Name server | ns-1667.awsdns-16.co.uk |
| ieeexplore.ieee.org | NS | Name server | ns-782.awsdns-33.net |
| ieeexplore.ieee.org | SOA | Start of Authority | ns-782.awsdns-33.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:ca00:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:1600:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:fa00:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:3800:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:2600:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:8600:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:dc00:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | AAAA | IPv6 address | 2600:9000:2246:c000:1e:d873:7a00:93a1 |
| ieeexplore.ieee.org | CNAME | Canonical name | d34ow7epij5zhk.cloudfront.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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-RELEASE | 87% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Java | Programming languages |
| MathJax 274 | JavaScript graphics |
| Pure CSS | UI frameworks |
| JSP | Web frameworks |
| Tealium | Tag managers, Customer data platform |
| Amazon Web Services | PaaS |
| Osano | Cookie compliance |
| Modernizr | JavaScript libraries |
| jQuery 3.5.1 | JavaScript libraries |
| Google Publisher Tag | Advertising |
| FingerprintJS 2 | JavaScript libraries, Browser fingerprinting |
| HSTS | Security |
| Amazon CloudFront | CDN |
| AWS Certificate Manager | SSL/TLS certificate authorities |
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.