# CVE-2011-4623: Integer overflow in n/a > Local attackers can cause a denial of service in rsyslog by triggering an integer overflow via a large file, leading to a daemon hang. - **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Sep 2012 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2011-4623, GHSA-j846-qfh4-5c92, RHSA-2012:0796 ## What is CVE-2011-4623? CVE-2011-4623 is a low-severity vulnerability in n/a, published on 25 Sep 2012. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Integer overflow in the rsCStrExtendBuf function in runtime/stringbuf.c in the imfile module in rsyslog 4.x before 4.6.6, 5.x before 5.7.4, and 6.x before 6.1.4 allows local users to cause a denial of service (daemon hang) via a large file, which triggers a heap-based buffer overflow. Weakness: CWE-189 ## Which versions are affected by CVE-2011-4623? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rsyslog` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog-gnutls` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog-gssapi` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog-mysql` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog-pgsql` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog-relp` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog-snmp` | Red Hat:enterprise_linux:6::client | All versions | 0:5.8.10-2.el6 | | `rsyslog` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog-gnutls` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog-gssapi` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog-mysql` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog-pgsql` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog-relp` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog-snmp` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.8.10-2.el6 | | `rsyslog` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog-gnutls` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog-gssapi` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog-mysql` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog-pgsql` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog-relp` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog-snmp` | Red Hat:enterprise_linux:6::server | All versions | 0:5.8.10-2.el6 | | `rsyslog` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | | `rsyslog-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | | `rsyslog-gnutls` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | | `rsyslog-gssapi` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | | `rsyslog-mysql` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | | `rsyslog-pgsql` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | | `rsyslog-relp` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | | `rsyslog-snmp` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.8.10-2.el6 | Products: Rsyslog Rsyslog. ## How do I fix CVE-2011-4623? Upgrade to a fixed version. ## Is CVE-2011-4623 being exploited? There is no known exploitation of CVE-2011-4623 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2019-17040](https://insights.sbomify.com/CVE-2019-17040/): Memory corruption in n/a (critical 9.8) - [CVE-2017-12588](https://insights.sbomify.com/CVE-2017-12588/): Other in n/a (critical 9.8) - [CVE-2008-5617](https://insights.sbomify.com/CVE-2008-5617/): Auth bypass in n/a (high 8.5) - [CVE-2014-3634](https://insights.sbomify.com/CVE-2014-3634/): Memory corruption in n/a (high 7.5) - [CVE-2013-4758](https://insights.sbomify.com/CVE-2013-4758/): Use after free in n/a (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2011-4623 and fix it if it is affected. What it is: CVE-2011-4623 is a low-severity vulnerability in n/a, published on 25 Sep 2012. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2011-4623 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2011-4623/ (Markdown: https://insights.sbomify.com/CVE-2011-4623/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2011-4623 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-4623 - OSV: https://osv.dev/vulnerability/CVE-2011-4623 --- From sbomify Insights: https://insights.sbomify.com/CVE-2011-4623/ Summaries are generated and may contain mistakes; the official description above is the record.