SNMP4J 3.13.1 | SNMP4J-Agent 3.10.1 | SNMP4J-Agent-DB 3.10.1 Releases

Announcements
1

The SNMP4J and SNMP4J-Agent APIs have been released with few security fixes and enhancements needed for the new SNMP4J-AgentX 4.2.0 release.

CHANGES SNMP4J 3.13.1

  • Fixed: AbstractTransportServerThread.sendMessage(..) re-connected a socket channel that was already published in the socket map of the transport mapping. That channel can be closed concurrently by the server thread, by the socket cleaner, and by other senders, and neither the state checks of sendMessage(..) nor SocketChannel.connect(..) hold a lock that prevents that. Because closing a non-blocking channel that has no reader or writer thread and is not registered with a selector closes its file descriptor immediately, the descriptor could be reused by an unrelated resource before the connect reached the operating system, which makes the connect fail with an error that does not refer to the intended connection at all. A new socket channel is opened now instead, which no other thread can reach before it is connected. A connect that is still in progress on an existing channel is left alone as before and the message is only queued on it.
  • Fixed: DefaultTcpTransportMapping.ServerThread opened a second Selector although the constructor of AbstractTransportServerThread had already opened one, so every call of listen() leaked a selector with its file descriptors.

CHANGES SNMP4J-Agent 3.10.1

  • SECURITY: DefaultAgentAuditPolicy now denies any modifying file operation, that is WRITE, CREATE, and DELETE, for the AgentPolicyProfile.FileAccess.WORKING_DIRECTORY_READONLY file access level. Before, such an operation was permitted for every file within the agent’s working directory, because the READ operation check was combined with the explicitly allowed files check only, instead of with the working directory check as well.
  • Improved: AgentConfigManager does no longer allow overwriting the auditPolicy once it has been set.

CHANGES SNMP4J-Agent-DB 3.10.1

  • SECURITY: Fixed SampleAgentConfig.properties to use SHA224 instead of SHA and restored SHA256AEAS128 full read access. Removed unrestricted write access with noAuthNoPriv access views on user SHA256AES128.
  • Updated: Dependency to SNMP4J-Agent 3.10.1 (SNMP4J 3.13.1).