{"uuid": "43be469d-cda5-4c18-a504-e8caaa60c3ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2008-2938", "type": "seen", "source": "https://github.com/rapid7/metasploit-framework/blob/master/modules/auxiliary/admin/http/trendmicro_dlp_traversal.rb", "content": "{\"actions\": [], \"aliases\": [], \"arch\": \"\", \"author\": [\"aushack \"], \"autofilter_ports\": [80, 8080, 443, 8000, 8888, 8880, 8008, 3000, 8443], \"autofilter_services\": [\"http\", \"https\"], \"check\": false, \"default_credential\": false, \"description\": \"This module tests whether a directory traversal vulnerability is present\\n        in Trend Micro DLP (Data Loss Prevention) Appliance v5.5 build <= 1294.\\n        The vulnerability appears to be actually caused by the Tomcat UTF-8\\n        bug which is implemented in module tomcat_utf8_traversal CVE 2008-2938.\\n        This module simply tests for the same bug with Trend Micro specific settings.\\n        Note that in the Trend Micro appliance, /etc/shadow is not used and therefore\\n        password hashes are stored and anonymously accessible in the passwd file.\", \"disclosure_date\": \"2009-01-09\", \"fullname\": \"auxiliary/admin/http/trendmicro_dlp_traversal\", \"is_install_path\": true, \"mod_time\": \"2026-06-17 11:11:50 +0000\", \"name\": \"TrendMicro Data Loss Prevention 5.5 Directory Traversal\", \"needs_cleanup\": false, \"notes\": {\"Reliability\": [], \"SideEffects\": [\"ioc-in-logs\"], \"Stability\": [\"crash-safe\"]}, \"path\": \"/modules/auxiliary/admin/http/trendmicro_dlp_traversal.rb\", \"platform\": \"\", \"post_auth\": false, \"rank\": 300, \"ref_name\": \"admin/http/trendmicro_dlp_traversal\", \"references\": [\"URL-http://tomcat.apache.org/\", \"OSVDB-47464\", \"OSVDB-73447\", \"CVE-2008-2938\", \"URL-http://www.securityfocus.com/archive/1/499926\", \"EDB-17388\", \"BID-48225\"], \"rport\": 8443, \"session_types\": false, \"targets\": null, \"type\": \"auxiliary\"}", "creation_timestamp": "2026-09-08T06:46:50.497542Z"}