CVE-2003-0628
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 · uneditedPeopleSoft Gateway Administration servlet (gateway.administration) in PeopleTools 8.43 and earlier allows remote attackers to obtain the full pathnames for server-side include (SSI) files via an HTTP request with an invalid value.
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 PeopleSoft Gateway Administration servlet (gateway.administration) in PeopleTools 8.43 and earlier exposes full file system pathnames for server-side include (SSI) files through a crafted HTTP request containing an invalid value, enabling remote attackers to perform path disclosure/information gathering.
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= 8.4= 8.10= 8.11= 8.12= 8.13= 8.14= 8.15= 8.16= 8.17= 8.18= 8.19= 8.20CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 PeopleTools installation and versionLocate the PeopleTools installation directory and check the version information file or registry entry that contains the PeopleTools version numberAffected if The installed PeopleTools version is 8.43 or earlier, or matches any of these: 8.4, 8.10, 8.11, 8.12, 8.13, 8.14, 8.15, 8.16, 8.17, 8.18, 8.19, 8.20
-
Locate the PeopleSoft Gateway servletSearch the application server or web server configuration for the gateway.administration servlet mappingAffected if The gateway.administration servlet is deployed and accessible on the application server
-
Determine servlet accessibilityCheck the web server or application server configuration to see if the gateway.administration servlet is exposed to network requests without authenticationAffected if The servlet is accessible remotely without requiring authentication
-
Test for path disclosure vulnerabilitySend an HTTP request to the gateway.administration servlet endpoint with a malformed or invalid SSI parameter value and observe if full filesystem pathnames are returned in the responseAffected if The response contains absolute filesystem paths that reveal the server's directory structure
The environment is affected if running PeopleTools version 8.43 or earlier with the gateway.administration servlet exposed and responding to crafted requests with filesystem path information
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 dataUpgrade PeopleTools to a version newer than 8.43 that includes the security patch, or implement input validation and access controls on the gateway.administration servlet to prevent path disclosure.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0628 — 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-2003-0628 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