---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Required JMS connection factories

# Required JMS connection factories {#ariaid-title1}

Release version: Australia  
Updated March 13, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The mid.property.jms.command.allowed_factory_names property controls the Java Messaging Service (JMS) connection factories that the MID Server can use.
This property controls the Java Messaging Service (JMS) connection factories that the MID Server can use. It is intended for a few select factories needed by plugins for JMS activity or action. Including additional factories could
be a step in a chain of attack for vulnerabilities such as JNDI insertion that rely on capabilities an attacker can leverage in allowed factories. To prevent the possibility of any leveraged vulnerability, do not include factories
beyond the necessary defaults.

Review the list of names provided to the mid property mid.property.jms.command.allowed_factory_names. Ensure any additional factory names beyond the default of <kbd class="ph userinput">connectionFactory, queueConnectionFactory, topicConnectionFactory</kbd> are necessary.

See the following documentation for updating this and other mid server properties: [MID Server properties](https://www.servicenow.com/docs/access?context=r_MIDServerProperties&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US)

## More information {#sc-required-jms-connection-factories-plugin-applicability-mid-server__section_qhx_1b1_xwb}

{#sc-required-jms-connection-factories-plugin-applicability-mid-server__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | mid.property.jms.command.allowed_factory_names |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | string |
| Default value | connectionFactory, queueConnectionFactory, topicConnectionFactory |
| Recommended value | connectionFactory, queueConnectionFactory, topicConnectionFactory |
| Category | [Access control](https://www.servicenow.com/docs/UcoTP53NgzpgtyyAIm1CdQ "The access control category audits the process of protecting resources from unauthorized access through granting and denying requests based on a permission model. This includes ensuring an entity accessing a resource holds valid credentials to do so, creating and protecting a well-defined set of roles or permissions and ensuring role or permission controls are protected from replay and tampering.") |
| Security risk | * Severity score: 4.1 * CVSS score: Medium * Security risk details: Expanding the set of Java Messaging Service (JMS) connection factories beyond the necessary defaults introduces a significant risk because it increases the attack surface for exploitation techniques such as JNDI injection. Allowing additional factories can enable attackers to leverage insecure configurations or vulnerabilities in messaging components as part of a broader attack chain, potentially leading to remote code execution or system compromise. Restricting factories to only those required by core functionality is essential to maintain a secure posture. {#sc-required-jms-connection-factories-plugin-applicability-mid-server__ul_g1g_3sf_xwb} |
| Dependencies and prerequisites | None |
[ ]

{#sc-required-jms-connection-factories-plugin-applicability-mid-server__table_ajc_b43_3kb}