Website Vulnerability Scanner Report
https://www.liiklusvalve.ee
Summary
Overall risk level: Risk ratings: Scan information:
High High: 1 Start time: 2021-11-06 03:00:10 UTC+02
Medium: 0 Finish time: 2021-11-06 03:01:07 UTC+02
Low: 3 Scan duration: 57 sec
Info: 4 Tests performed: 8/8
Scan status: Finished
Findings
Vulnerabilities found for server-side software
Risk Affected
CVSS CVE Summary Exploit
Level software
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS)
jQuery
4.3 CVE-2015-9251 attacks when a cross-domain Ajax request is performed without the N/A
1.12.1
dataType option, causing text/javascript responses to be executed.
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other
products, mishandles jQuery.extend(true, {}, ...) because of
jQuery
4.3 CVE-2019-11358 Object.prototype pollution. If an unsanitized source object contained N/A
1.12.1
an enumerable __proto__ property, it could extend the native
Object.prototype.
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
jQuery
4.3 CVE-2020-11022 one of jQuery's DOM manipulation methods (i.e. .html(), .append(), N/A
1.12.1
and others) may execute untrusted code. This problem is patched in
jQuery 3.5.0.
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, jQuery
4.3 CVE-2020-11023 N/A
passing HTML containing 1.12.1
Details
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 himself) for any of these vulnerabilities and use it to
attack the system.
Recommendation:
We recommend you to upgrade the affected software to the latest version in order to eliminate the risk of these vulnerabilities.
Classification:
CWE : CWE-1026
OWASP Top 10 - 2013 : A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2017 : A9 - Using Components with Known Vulnerabilities
1/4
Missing security header: Content-Security-Policy CONFIRMED
URL Evidence
https://www.liiklusvalve.ee Response headers do not include the HTTP Content-Security-Policy security header
Details
Risk description:
The Content-Security-Policy (CSP) header activates a protection mechanism implemented in web browsers which prevents exploitation
of Cross-Site Scripting vulnerabilities (XSS). 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.
Read more about CSP:
https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
Missing security header: Referrer-Policy CONFIRMED
URL Evidence
https://www.liiklusvalve.ee Response headers do not include the Referrer-Policy HTTP security header
Details
Risk description:
The Referrer-Policy HTTP header controls how much referrer information the browser will send with each request originated from the
current web application.
For instance, if a user visits the web page "http://example.com/pricing/" and it 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.
Read more:
https://developer.mozilla.org/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
Server software and technology found CONFIRMED
Software / Version Category
IIS 10.0 Web Servers
Microsoft ASP.NET 4.0.30319 Web Frameworks
Google Analytics UA Analytics
jQuery 3.5.1 JavaScript Frameworks
jQuery UI 1.12.1 JavaScript Frameworks
2/4
Details
Risk description:
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.
More information about this issue:
https://owasp.org/www-project-web-security-testing-guide/stable/4-Web_Application_Security_Testing/01-Information_Gathering/02-
Fingerprint_Web_Server.html.
Classification:
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
Screenshot:
Figure 1. Website Screenshot
Website is accessible.
Nothing was found for client access policies.
Nothing was found for robots.txt file.
Nothing was found for use of untrusted certificates.
Scan coverage information
List of tests performed (8/8)
Checking for website accessibility...
Checking for missing HTTP header - Content Security Policy...
Checking for missing HTTP header - Referrer...
Checking for website technologies...
Checking for vulnerabilities of server-side software...
3/4
Checking for client access policies...
Checking for robots.txt file...
Checking for use of untrusted certificates...
Scan parameters
Website URL: https://www.liiklusvalve.ee
Scan type: Light
Authentication: False
Scan stats
URLs spidered: 1
Total number of HTTP request errors: 0
Total number of HTTP requests: 8
Unique Injection Points Detected: 20
4/4
Majandus- ja Kommunikatsiooniministeerium
19.11.2021
Pakkumus JQuery uuendamiseks
Vastavalt Website Vulnerability Scanner raportile, vajab uuendamist Liiklus-
järelvalve infosüsteemi JQuery UI versioon 1.12.1. Pakkumuses esitatud
versiooni uuendamise arendustöö käigus vahetatakse aegunud versioon uue
vastu välja ja testitakse, et kõik third party library’d jäid tööle.
Töö Tunnid Maksumus
(EUR)
JQuery versiooni uuenamine 80 3 200
Kokku 3 200 EUR
Tööde maksumus
Versiooni uuendamiseks kulub 80 tundi. Tööde maksumus on 3 200 Eurot, millele
lisandub käibemaks.
Ajakava
JQuery uuendamisega seotud tööd valmivad hiljemalt 21.01.2022.
Maksetingimused
Majandus- ja Kommunikatsiooniministeerium tasub Uptime OÜ-le vastavalt
esitatud arvele, mis esitatakse peale tööde üleandmis-vastuvõtmisakti
allkirjastamist.
Pakkumuse kehtivus
Pakkumine on jõus kuni 01.12.2021. Pakkumus loetakse aktsepteerituks kirjaliku
kinnituse jõudmisel e-posti aadressile
[email protected].
Kontaktandmed: Arigio Somelar
Projektijuht
[email protected]
Tel. 55 905 941
Skype: arigio.somelar
Website Vulnerability Scanner Report
https://www.liiklusvalve.ee
Summary
Overall risk level: Risk ratings: Scan information:
High High: 1 Start time: 2021-11-06 03:00:10 UTC+02
Medium: 0 Finish time: 2021-11-06 03:01:07 UTC+02
Low: 3 Scan duration: 57 sec
Info: 4 Tests performed: 8/8
Scan status: Finished
Findings
Vulnerabilities found for server-side software
Risk Affected
CVSS CVE Summary Exploit
Level software
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS)
jQuery
4.3 CVE-2015-9251 attacks when a cross-domain Ajax request is performed without the N/A
1.12.1
dataType option, causing text/javascript responses to be executed.
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other
products, mishandles jQuery.extend(true, {}, ...) because of
jQuery
4.3 CVE-2019-11358 Object.prototype pollution. If an unsanitized source object contained N/A
1.12.1
an enumerable __proto__ property, it could extend the native
Object.prototype.
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
jQuery
4.3 CVE-2020-11022 one of jQuery's DOM manipulation methods (i.e. .html(), .append(), N/A
1.12.1
and others) may execute untrusted code. This problem is patched in
jQuery 3.5.0.
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, jQuery
4.3 CVE-2020-11023 N/A
passing HTML containing 1.12.1
Details
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 himself) for any of these vulnerabilities and use it to
attack the system.
Recommendation:
We recommend you to upgrade the affected software to the latest version in order to eliminate the risk of these vulnerabilities.
Classification:
CWE : CWE-1026
OWASP Top 10 - 2013 : A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2017 : A9 - Using Components with Known Vulnerabilities
1/4
Missing security header: Content-Security-Policy CONFIRMED
URL Evidence
https://www.liiklusvalve.ee Response headers do not include the HTTP Content-Security-Policy security header
Details
Risk description:
The Content-Security-Policy (CSP) header activates a protection mechanism implemented in web browsers which prevents exploitation
of Cross-Site Scripting vulnerabilities (XSS). 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.
Read more about CSP:
https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
Missing security header: Referrer-Policy CONFIRMED
URL Evidence
https://www.liiklusvalve.ee Response headers do not include the Referrer-Policy HTTP security header
Details
Risk description:
The Referrer-Policy HTTP header controls how much referrer information the browser will send with each request originated from the
current web application.
For instance, if a user visits the web page "http://example.com/pricing/" and it 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.
Read more:
https://developer.mozilla.org/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
Server software and technology found CONFIRMED
Software / Version Category
IIS 10.0 Web Servers
Microsoft ASP.NET 4.0.30319 Web Frameworks
Google Analytics UA Analytics
jQuery 3.5.1 JavaScript Frameworks
jQuery UI 1.12.1 JavaScript Frameworks
2/4
Details
Risk description:
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.
More information about this issue:
https://owasp.org/www-project-web-security-testing-guide/stable/4-Web_Application_Security_Testing/01-Information_Gathering/02-
Fingerprint_Web_Server.html.
Classification:
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
Screenshot:
Figure 1. Website Screenshot
Website is accessible.
Nothing was found for client access policies.
Nothing was found for robots.txt file.
Nothing was found for use of untrusted certificates.
Scan coverage information
List of tests performed (8/8)
Checking for website accessibility...
Checking for missing HTTP header - Content Security Policy...
Checking for missing HTTP header - Referrer...
Checking for website technologies...
Checking for vulnerabilities of server-side software...
3/4
Checking for client access policies...
Checking for robots.txt file...
Checking for use of untrusted certificates...
Scan parameters
Website URL: https://www.liiklusvalve.ee
Scan type: Light
Authentication: False
Scan stats
URLs spidered: 1
Total number of HTTP request errors: 0
Total number of HTTP requests: 8
Unique Injection Points Detected: 20
4/4
Hankelepingu lisa 1
Lähteülesanne
Töö käigus tuleb uuendada liiklusjärelevalve infosüsteemi (edaspidi LJVIS) lähtekoodis
Javascripti teek JQuery UI. Seni on LJVISes kasutusel JQuery UI versioon 1.12.1. Töö käigus
tuleb see asendada uuema stabiilse versiooni vastu. Peale versiooniuuendust tuleb läbi viia
LJVISi funktsionaalsuse testimine, veendumaks, et kõik LJVISe funktsionaalsused on
töökorras.
Peale JQuery UI teegi uuendamist ei tohi turvaraportis (Lisa 3) olla suure ja keskmise
riskiastmega turvaprobleeme.
Arendustööde hankeleping nr. 7/1.9-21/21-451-1
Tallinnas, 24.11.2021
Majandus- ja Kommunikatsiooniministeerium, registrikood 70003158, asukohaga Suur-
Ameerika 1, Tallinn 10122, mida esindab põhimääruse alusel kantsler Ando Leppiman
(edaspidi Tellija)
ja
Uptime OÜ, registrikood 10308733, asukoht Pärnu mnt 158, Tallinn 11317, mida esindab
juhatuse liige Eero Tohver (edaspidi Täitja), keda edaspidi nimetatakse üheskoos ka Pooled ja
eraldi Pool,
sõlmivad käesoleva hankelepingu (edaspidi Leping) alljärgnevas:
1. Üldsätted ja Lepingu alus
1.1. Leping sõlmitakse Tellija korraldatud lihthanke "Liiklusjärelevalve infosüsteemi
arendus- ja hooldusteenus 2“ (viitenumber 202118) tulemusena 04.12.2018. a sõlmitud
raamlepingu 1.9-21/18-429-1 (edaspidi Raamleping) alusel.
1.2. Lepingu dokumendid koosnevad Raamlepingust, Raamlepingu lisadest, Lepingust,
Lepingu lisadest ning Lepingu võimalikest muudatustest, milles lepitakse kokku pärast
Lepingule allakirjutamist.
1.3. Käesoleva Lepingu allakirjutamise hetkel on Lepingule lisatud:
Lisa 1 – Lähteülesanne;
Lisa 2 – Pakkumus;
Lisa 3 – Turvaraport.
2. Lepingu objekt, Töö teostamise tähtaeg ja maksumus
2.1. Lepingu objektiks on liiklusjärelevalve infosüsteemis Javascripti teegi JQuery UI
uuendamine (edaspidi Töö) vastavalt Lepingu Lisale 1 ja Lisale 2.
2.2. Täitja kohustub Töö üle andma 21.01.2022.
2.3. Lepingu maht on 80 töötundi ja Lepingu maksumus käibemaksuta on 3200 eurot.
3. Lepingu eseme üleandmine ja vastuvõtmine
Töö antakse Tellijale üle vastavalt Raamlepingu punktidele 6.2 ja 6.3.
4. Poolte volitatud esindajad
4.1. Tellija volitatud esindaja Lepingu tingimuste täitmisel, kontrollimisel ja Töö
vastuvõtmisel on Verner Eiber (telefon +372 6256 496, e-post
[email protected]).
4.2. Täitja volitatud esindaja Lepingu tingimuste täitmisel, kontrollimisel ja Töö üleandmisel
on Arigio Somelar (telefon +372 55905 941, e-post
[email protected]).
4.3. Juhul, kui Tellija või Täitja asendab oma esindaja teisega, teatab ta sellest teisele Poolele
viivitamatult kirjalikult.
-1-
Poolte allkirjad:
Tellija: Täitja:
Majandus- ja Kommunikatsiooni- Uptime OÜ
ministeerium
Ando Leppiman Eero Tohver
Kantsler Juhatuse liige
-2-