CVE-2005-2256
published 2005-07-13CVE-2005-2256: Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remote attackers to access arbitrary files via "%2e%2e%2f" (encoded dot dot)…
PriorityP430medium5CVSS 2.0
AVNACLAuNCPINAN
EXPLOIT
EPSS
4.64%
90.6th percentile
Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remote attackers to access arbitrary files via "%2e%2e%2f" (encoded dot dot) sequences in the formLanguage parameter.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | phppgadmin | < phppgadmin 3.5.4-1 (forky) | phppgadmin 3.5.4-1 (forky) |
| phppgadmin | phppgadmin | — | — |
| phppgadmin | phppgadmin | — | — |
| phppgadmin | phppgadmin | — | — |
| phppgadmin | phppgadmin | — | — |
| phppgadmin | phppgadmin | — | — |
| phppgadmin | phppgadmin | — | — |
| phppgadmin_project | phppgadmin | >= 0 < 3.5.4-1 | 3.5.4-1 |
| phppgadmin_project | phppgadmin | >= 0 < 3.5.4-1 | 3.5.4-1 |
CVSS provenance
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv5.0MEDIUM
vendor_debian5.0MEDIUM
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-pfcx-fx8j-6wch: Encoded directory traversal vulnerability in phpPgAdmin 3
ghsa_unreviewed·2022-05-01
CVE-2005-2256 [MEDIUM] GHSA-pfcx-fx8j-6wch: Encoded directory traversal vulnerability in phpPgAdmin 3
Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remote attackers to access arbitrary files via "%2e%2e%2f" (encoded dot dot) sequences in the formLanguage parameter.
OSV
CVE-2005-2256: Encoded directory traversal vulnerability in phpPgAdmin 3
osv·2005-07-13·CVSS 5.0
CVE-2005-2256 [MEDIUM] CVE-2005-2256: Encoded directory traversal vulnerability in phpPgAdmin 3
Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remote attackers to access arbitrary files via "%2e%2e%2f" (encoded dot dot) sequences in the formLanguage parameter.
Debian
CVE-2005-2256: phppgadmin - Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remo...
vendor_debian·2005·CVSS 5.0
CVE-2005-2256 [MEDIUM] CVE-2005-2256: phppgadmin - Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remo...
Encoded directory traversal vulnerability in phpPgAdmin 3.1 to 3.5.3 allows remote attackers to access arbitrary files via "%2e%2e%2f" (encoded dot dot) sequences in the formLanguage parameter.
Scope: local
forky: resolved (fixed in 3.5.4-1)
sid: resolved (fixed in 3.5.4-1)
trixie: resolved (fixed in 3.5.4-1)
No detection rules found.
No writeups or analysis indexed.
CWE
Improper Handling of URL Encoding (Hex Encoding)
mitre_cwe·CVSS 7.5
[HIGH] CWE-177 Improper Handling of URL Encoding (Hex Encoding)
CWE-177: Improper Handling of URL Encoding (Hex Encoding)
The product does not properly handle when all or part of an input has been URL encoded.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Unexpected State.
Potential Mitigations:
[Architecture and Design] Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
[Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including le
CWE
Encoding Error
mitre_cwe
CWE-172 Encoding Error
CWE-172: Encoding Error
The product does not properly encode or decode the data, resulting in unexpected values.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Unexpected State.
Potential Mitigations:
[Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an e
http://archives.neohapsis.com/archives/dailydave/2005-q3/0010.htmlhttp://secunia.com/advisories/15941http://secunia.com/advisories/16116http://securitytracker.com/id?1014414http://sourceforge.net/project/shownotes.php?release_id=342261http://www.debian.org/security/2005/dsa-759http://www.securityfocus.com/bid/14142http://www.vuxml.org/freebsd/88188a8c-eff6-11d9-8310-0001020eed82.htmlhttp://archives.neohapsis.com/archives/dailydave/2005-q3/0010.htmlhttp://secunia.com/advisories/15941http://secunia.com/advisories/16116http://securitytracker.com/id?1014414http://sourceforge.net/project/shownotes.php?release_id=342261http://www.debian.org/security/2005/dsa-759http://www.securityfocus.com/bid/14142http://www.vuxml.org/freebsd/88188a8c-eff6-11d9-8310-0001020eed82.html
2005-07-13
Published