CVE-2022-40468: High severity Tinyproxy Project Tinyproxy vulnerability

Published Sep 19, 2022
·
Updated

Last updated 6 January 2025

Other sources

Potential leak of left-over heap data if custom error page templates containing special non-standard variables are used. Tinyproxy commit 84f203f and earlier use uninitialized buffers in processrequest() function.

Affected Software

2 affected componentsFixes available
debian/tinyproxy<=1.10.0-5
1.10.0-5+deb11u11.11.1-2.1+deb12u11.11.2-1
Tinyproxy Project Tinyproxy<=1.11.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/tinyproxy to a version that resolves this vulnerability.

    Fixed in 1.10.0-5+deb11u1Fixed in 1.11.1-2.1+deb12u1Fixed in 1.11.2-1
  2. Upgrade

    Upgrade tinyproxy to a version that resolves this vulnerability.

    Patch 84f203f
  3. Compensating control

    If custom error page templates using special non-standard variables are used, avoid them or remove the non-standard variables to prevent potential leakage of left-over heap data.

Event History

Sep 19, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Dec 9, 2024
Data Sourced
via Launchpad·08:08 AM
Description
Jan 10, 2025
Data Sourced
via Ubuntu·12:14 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2022-40468?

CVE-2022-40468 is classified as a medium severity vulnerability due to the potential leak of sensitive data from uninitialized buffers.

2

How do I fix CVE-2022-40468?

To fix CVE-2022-40468, update Tinyproxy to version 1.10.0-5+deb11u1, 1.11.1-2.1+deb12u1, or 1.11.2-1.

3

What are the affected versions for CVE-2022-40468?

CVE-2022-40468 affects Tinyproxy versions up to and including 1.11.1.

4

What specifically causes CVE-2022-40468?

CVE-2022-40468 is caused by the use of uninitialized buffers in the process_request() function when custom error page templates are used.

5

Is there a workaround for CVE-2022-40468?

Currently, no specific workaround is recommended for CVE-2022-40468 other than updating to a patched version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203