Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.5

Zotero Connector

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Zotero Connector is a browser plugin that is used for collecting, organizing, and sharing research sources on specific web browsers. This technology works in conjunction with the Zotero standalone software. Zotero Connector can sense browsing content, detect available translations, store and retrieve connector preferences, and send translated items to Zotero standalone. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.4
Decision Date:	04/22/2025 at 13:34:35 UTC
Aliases:	Zotero Connector Browser Plugin
Introduced By:	TRM Request
Vendor Name:	Corporation for Digital Scholarship

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
5.x (Chrome)	08/18/2021
5.x (Firefox)	08/18/2021
5.x (Safari)	08/18/2021

Current Decision Matrix (04/21/2025)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2024

CY2025

CY2026

Future>

Release

5.x (Chrome)

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]

5.x (Firefox)

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]

5.x (Safari)

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]

Note:

At the time of writing, version 5.0.163 is the most current version, released 04/17/2025.

Decision Constraints


[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.

Name	Description
No components have been identified for this entry.


Collaboration and Electronic Workplace Productivity Software	Miscellaneous Productivity Tools and Utilities

General Analysis

Adoption Benefits

At the time of writing, there are a limited number of TRM options providing this functionality. The addition of this technology will provide end users with multiple viable options.
This technology has a comprehensive set of documentation.
This technology is available at no cost through open-source licensing and supports VA's open-source initiative.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.

Adoption Risks

This technology can potentially use Node.js , which users must ensure that authorized versions are utilized.
This technology can potentially use ws (an open source WebSocket client and server for Node.js) and tough-cookie, which are not listed on the TRM.
IPR/SAR Adoption Risk - Zotero Connector Browser Extension is not FIPS 140-2 (or its successor) certified. According to the vendor, “all data is encrypted in transit with current best practices and stored within the Amazon cloud, where access is tightly restricted to the small number of Zotero staff members who need access to maintain the service.”
IPR/SAR Adoption Risk - As an open-source product, Zotero Connector Browser Extension is supported through Zotero’s online community-based forum.
IPR/SAR Adoption Risk - One Critical findings from Chrome permissions were found: http://*/* - Gives your extension access to run on all "http" sites.
IPR/SAR Adoption Risk - One High findings from Chrome permissions were found: declarativeNetRequest - The chrome.declarativeNetRequest API is used for blocking or modifying network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, thus providing more privacy
IPR/SAR Adoption Risk - Eight Medium findings from Chrome permissions were found: webRequestBlocking - Required if the extension uses the chrome.webRequest API in a blocking fashion. /// webRequest - The chrome.webRequest API is used for observing and analyzing traffic, as well as intercepting, blocking, or modifying requests in-flight. /// Tabs - Gives your extension access to privileged fields of the Tab objects used by several APIs including chrome.tabs and chrome.windows. In many circumstances your extension will not need to declare the "tabs" permission to make use of these APIs. /// webNavigation - Gives your extension access to the chrome.webNavigation API. /// storage - Gives your extension access to the chrome.storage API. /// Cookies - The chrome.cookies API is used for querying and modifying cookies, and for being notified when they change. /// management - Gives your extension access to the chrome.management API. /// clipboardWrite - Indicates the extension or app uses document.execCommand("copy") or document.execCommand("cut"). This permission is required for hosted apps; it's recommended for extensions and packaged apps.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
All system media will be properly managed and controlled in accordance with VA Handbook 6500.
Both the hardware and software are configured for operational use throughout the duration of the testing.
This technology can potentially use Node Package Manager (NPM), which users must ensure that authorized versions are utilized.

Architectural Benefits

This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

- The information contained on this page is accurate as of the Decision Date (04/22/2025 at 13:34:35 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.5

General Information

Vendor Release Information

Current Decision Matrix (04/21/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 25.5

General Information

Vendor Release Information

Current Decision Matrix (04/21/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework