Browser vulnerabilities database
This small library detects vulnerable operating systems and browsers based on browser user-agent string. No active checks are included.
from browser_vulnerabilities import BrowserVulnerability
ua1 = 'Mozilla/5.0 (Windows NT 6.3; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0'
ua2 = 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Firefox/27.0'
bv = BrowserVulnerability(ua1)
print bv.vulnerabilities()
# {'priority': 'recommended', 'readable_version': 'Firefox older than 27.0',
# 'name': 'Firefox', 'version__smaller': '27.0'}
bv = BrowserVulnerability(ua2)
print bv.vulnerabilities()
# False
Minimal database is available in browser_vulnerabilities/data.py file. The database is updated manually. Order of criteria is important. The most important and most strict criteria should be first. Matching is aborted on the first hit.
Mandatory keywords:
platform / flavor / name: first two are for OS, and name for browser (feature of httpagentparser)
priority:
“mandatory” - user action is required, and actions should be either denied or delayed with message.
“recommended” - updating is highly recommended but not mandatory.
“optional” - the warning should be shown to user only when user requests more information.
Optional keywords:
version__smaller: any version larger than this will not match the rule.
version__larger: any version smaller than this will not match the rule.
version__extra: compiled re for additional checks.
vuln: link to related website describing the vulnerabilities / why specific update is important.
readable_name: user-readable product name
version: user-readable version criteria for warnings
License
Licensed under MIT license:
Copyright (c) 2014 Olli jarva olli@jarva.fi
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Metadata
Release files for browser_vulnerabilities 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| browser_vulnerabilities-0.1.0.tar.gz | 4.3 kB | Without provenance | Details for browser_vulnerabilities-0.1.0.tar.gz |
Release files / browser_vulnerabilities-0.1.0.tar.gz
| Download URL | browser_vulnerabilities-0.1.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d426398162228de3a975568c81bfc5065c6649e38e34e0b3729cb5a7a1eb1b7
|
|
BLAKE2b-256 checksum How to use checksums |
b1d541b2c3abb9bf37c870b481d2509596048947e6e9b9068c23ecba67242a6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for browser_vulnerabilities 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.