Fluentd's Monitor Agent plugin (`in_monitor_agent`) exposes internal metrics and plugin information via a REST API. It was discovered that the API response (`/api/plugins.json` and related endpoints) unintentionally includes internal instance variables of loaded plugins. If any plugins store sensitive information—such as database passwords, API keys, or cloud credentials—in its instance variables, this information may be exposed in plain text to any user or system that has HTTP access to the Monitor Agent API. ### Impact This vulnerability allows for unauthorized information disclosure. An attacker who can reach the Monitor Agent API port (default: `24220`) can potentially extract sensitive credentials used by other Fluentd plugins. The impact severity depends highly on the network configuration (whether the Monitor Agent port is exposed to untrusted networks) and the specific plugins configured in the Fluentd instance. ### Patches: v1.19.3 ### Workarounds If usesrs cannot immediately update Fluentd to the patched version, they can mitigate this risk by strictly controlling access to the Monitor Agent port. Ensure the Monitor Agent is only bound to `localhost` (`127.0.0.1`) rather than `0.0.0.0`. ``` <source> @type monitor_agent bind 127.0.0.1 port 24220 </source> ``` Use firewall rules (e.g., iptables, AWS Security Groups) to block access to the Monitor Agent port (`24220`) from untrusted networks or instances.
Fluentd's Monitor Agent plugin (`in_monitor_agent`) exposes internal metrics and plugin information via a REST API. It was discovered that the API response (`/api/plugins.json` and related endpoints) unintentionally includes internal instance variables of loaded plugins. If any plugins store sensitive information—such as database passwords, API keys, or cloud credentials—in its instance variables, this information may be exposed in plain text to any user or system that has HTTP access to the Monitor Agent API. ### Impact This vulnerability allows for unauthorized information disclosure. An attacker who can reach the Monitor Agent API port (default: `24220`) can potentially extract sensitive credentials used by other Fluentd plugins. The impact severity depends highly on the network configuration (whether the Monitor Agent port is exposed to untrusted networks) and the specific plugins configured in the Fluentd instance. ### Patches: v1.19.3 ### Workarounds If usesrs cannot immediately update Fluentd to the patched version, they can mitigate this risk by strictly controlling access to the Monitor Agent port. Ensure the Monitor Agent is only bound to `localhost` (`127.0.0.1`) rather than `0.0.0.0`. ``` <source> @type monitor_agent bind 127.0.0.1 port 24220 </source> ``` Use firewall rules (e.g., iptables, AWS Security Groups) to block access to the Monitor Agent port (`24220`) from untrusted networks or instances.
Update fluentd to 1.19.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanFluentd is Vulnerable to Exposure of Sensitive Information via Monitor Agent API affects fluentd (rubygems). Severity is high. Fluentd's Monitor Agent plugin (`in_monitor_agent`) exposes internal metrics and plugin information via a REST API. It was discovered that the API response (`/api/plugins.json` and related endpoints) unintentionally includes internal instance variables of loaded plugins. If any plugins store sensitive information—such as database passwords, API keys, or cloud credentials—in its instance variables, this information may be exposed in plain text to any user or system that has HTTP access to the Monitor Agent API. ### Impact This vulnerability allows for unauthorized information disclosure. An attacker who can reach the Monitor Agent API port (default: `24220`) can potentially extract sensitive credentials used by other Fluentd plugins. The impact severity depends highly on the network configuration (whether the Monitor Agent port is exposed to untrusted networks) and the specific plugins configured in the Fluentd instance. ### Patches: v1.19.3 ### Workarounds If usesrs cannot immediately update Fluentd to the patched version, they can mitigate this risk by strictly controlling access to the Monitor Agent port. Ensure the Monitor Agent is only bound to `localhost` (`127.0.0.1`) rather than `0.0.0.0`. ``` <source> @type monitor_agent bind 127.0.0.1 port 24220 </source> ``` Use firewall rules (e.g., iptables, AWS Security Groups) to block access to the Monitor Agent port (`24220`) from untrusted networks or instances.
AI coding agents often install or upgrade packages automatically in rubygems. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| fluentdrubygems | <=1.19.2 | 1.19.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate fluentd to 1.19.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanFluentd is Vulnerable to Exposure of Sensitive Information via Monitor Agent API affects fluentd (rubygems). Severity is high. Fluentd's Monitor Agent plugin (`in_monitor_agent`) exposes internal metrics and plugin information via a REST API. It was discovered that the API response (`/api/plugins.json` and related endpoints) unintentionally includes internal instance variables of loaded plugins. If any plugins store sensitive information—such as database passwords, API keys, or cloud credentials—in its instance variables, this information may be exposed in plain text to any user or system that has HTTP access to the Monitor Agent API. ### Impact This vulnerability allows for unauthorized information disclosure. An attacker who can reach the Monitor Agent API port (default: `24220`) can potentially extract sensitive credentials used by other Fluentd plugins. The impact severity depends highly on the network configuration (whether the Monitor Agent port is exposed to untrusted networks) and the specific plugins configured in the Fluentd instance. ### Patches: v1.19.3 ### Workarounds If usesrs cannot immediately update Fluentd to the patched version, they can mitigate this risk by strictly controlling access to the Monitor Agent port. Ensure the Monitor Agent is only bound to `localhost` (`127.0.0.1`) rather than `0.0.0.0`. ``` <source> @type monitor_agent bind 127.0.0.1 port 24220 </source> ``` Use firewall rules (e.g., iptables, AWS Security Groups) to block access to the Monitor Agent port (`24220`) from untrusted networks or instances.
AI coding agents often install or upgrade packages automatically in rubygems. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| fluentdrubygems | <=1.19.2 | 1.19.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard