CVE-2009-2301
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe radware AppWall Web Application Firewall (WAF) 1.0.2.6, with Gateway 4.6.0.2, allows remote attackers to read source code via a direct request to (1) funcs.inc, (2) defines.inc, or (3) msg.inc in Management/.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Radware AppWall WAF 1.0.2.6 with Gateway 4.6.0.2 contains a path traversal/information disclosure vulnerability allowing remote attackers to retrieve source code by directly requesting .inc include files (funcs.inc, defines.inc, msg.inc) in the Management/ directory. These files are intended for server-side inclusion but are accessible via HTTP, exposing potentially sensitive application logic, credentials, or configuration details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.2.6= 4.6.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Radware productLocate the Radware AppWall or Gateway installation and determine the installed version number through the product's web interface, administrative console, or installed software listingAffected if The product is Radware AppWall version 1.0.2.6 or Radware Gateway version 4.6.0.2
-
Verify Management directory is HTTP accessibleUsing a web browser or curl command, attempt to access the Management/ directory path on the affected server (e.g., http://target/Management/)Affected if The Management directory returns an HTTP 200 response and is browsable or returns a directory listing
-
Test .inc file direct accessDirectly request each include file via HTTP: /Management/funcs.inc, /Management/defines.inc, /Management/msg.incAffected if Any .inc file returns HTTP 200 and displays source code instead of being processed server-side or blocked
-
Inspect exposed file contentsExamine the content of any accessible .inc files for sensitive data such as database credentials, API keys, internal paths, or application logicAffected if The .inc files contain credentials, configuration secrets, or sensitive application code that should not be publicly accessible
A user is affected if they are running Radware AppWall 1.0.2.6 or Gateway 4.6.0.2 AND the Management/ directory .inc files are directly accessible via HTTP, exposing source code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDeny direct HTTP access to all .inc files via web server configuration (e.g., Apache Deny from all, IIS request filtering), or move sensitive include files outside the web-accessible document root. If the product is end-of-life, upgrade to a supported version.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-2301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-2301 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data