<Past |
Future> |
5.x (Chrome) |
Approved w/Constraints [2, 3, 6, 10, 11, 12] |
Approved w/Constraints [2, 3, 6, 10, 11, 12] |
DIVEST [3, 10, 11, 12, 13, 14, 15] |
Authorized w/ Constraints (DIVEST) [3, 10, 11, 12, 13, 14, 15] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
5.x (Firefox) |
Approved w/Constraints [2, 3, 6, 10, 11, 12] |
Approved w/Constraints [2, 3, 6, 10, 11, 12] |
DIVEST [3, 10, 11, 12, 13, 14, 15] |
Authorized w/ Constraints (DIVEST) [3, 10, 11, 12, 13, 14, 15] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
5.x (Safari) |
Approved w/Constraints [2, 3, 6, 10, 11, 12] |
Approved w/Constraints [2, 3, 6, 10, 11, 12] |
DIVEST [3, 10, 11, 12, 13, 14, 15] |
Authorized w/ Constraints (DIVEST) [3, 10, 11, 12, 13, 14, 15] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Authorized w/ Constraints [3, 10, 11, 12, 14, 15, 16] |
Note: |
At the time of writing, version 5.0.163 is the most current version, released 04/17/2025. |
| | [2] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [3] | Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements. | | [6] | Users must ensure that Mozilla Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review (SAR), users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA
sensitive data in applications and devices that use Zotero Connector Browser
Plugin.
- Given that there is a lack of formal enterprise level support, it is important that
Zotero Connector Browser Plugin and Zotero.org be continually monitored for
vulnerabilities and updates.
| | [10] | Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations. | | [11] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [12] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [13] | Users must ensure that Mozilla Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that when using Node Packet Manager (NPM) and Node.js that authorized versions are utilized.
Users must not utilize ws (an open source WebSocket client and server for Node.js) and tough-cookie, as they are, at the time of writing, are not listed on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 certified cryptographic module to secure VA sensitive data in applications and devices that use Zotero Connector Browser Extension.
- Given that there is a lack of formal enterprise level support, it is important that Zotero Connector Browser Extension and Zotero.org be continually monitored for vulnerabilities and updates.
- Due to potential information security risks, Software as a Service (SaaS)/Platform as a Service (PaaS) solutions must complete the Business Integration and Outcomes Service (BIOS) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
- The Zotero Connector Browser Extension has ten permissions findings for Edge and Chrome. There was one Critical and four High risk findings found during the OWASP dependency check. The CVE’s found are the following: NVD - CVE-2023-26136 (nist.gov), NVD - CVE-2024-4068 (nist.gov), NVD - CVE-2023-43646 (nist.gov), NVD - CVE-2023-26115 (nist.gov), NVD - CVE-2024-37890 (nist.gov).
| | [14] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | [15] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [16] | Users must ensure that Mozilla Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that when using Node Packet Manager (NPM) and Node.js that authorized versions are utilized.
Users must not utilize ws (an open source WebSocket client and server for Node.js) and tough-cookie, as they are, at the time of writing, are not listed on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 (or its successor) certified cryptographic module to secure VA sensitive data in applications and devices that use Zotero Connector Browser Extension.
- Zotero`s paid staff developers provide direct, 24/7/365 support in the Zotero Forums. Per Zotero support, issues reported are often resolved within minutes, and bugs are often fixed the same day. Sensitive security issues can be reported to security@zotero.org.
- The Zotero Connector Browser Extension has ten permissions findings for Chrome. The permissions required by the extension are explained in Zotero’s privacy policy: https://www.zotero.org/support/privacy#zotero_connector
- There was one Medium risk finding found during the OWASP dependency check scans. The CVE’s found are the following: CVE-2025-26791. Developer states that they use the library to comply with Mozilla policies for sanitizing their HTML strings bundled with Zotero Connector. DOMPurify is used in its standard configuration. According to the developer the exploit doesn`t apply.
|
|