CVE-2014-4767
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 · uneditedIBM WebSphere Application Server (WAS) Liberty Profile 8.5.x before 8.5.5.3 does not properly use the Liberty Repository for feature installation, which allows remote authenticated users to execute arbitrary code via unspecified vectors.
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 confidenceIBM WebSphere Application Server Liberty Profile 8.5.x before 8.5.5.3 has a vulnerability in the Liberty Repository feature installation mechanism. The improper use of the repository allows authenticated remote users to execute arbitrary code through unspecified vectors related to feature installation.
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.5.0.0= 8.5.0.1= 8.5.0.2= 8.5.5.0= 8.5.5.1= 8.5.5.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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 the installed IBM WebSphere Application Server versionRun the command 'productInfo version' from the Liberty Profile bin directory, or check the installation directory for version.info fileAffected if The version is 8.5.0.0, 8.5.0.1, 8.5.0.2, 8.5.5.0, 8.5.5.1, or 8.5.5.2 (any version before 8.5.5.3 in the 8.5.x line)
-
Confirm the Liberty Profile editionCheck if the installation is the Liberty Profile by verifying the server.xml file exists in the wlp/usr/servers/<serverName>/ directoryAffected if The server uses Liberty Profile (not full WebSphere Application Server)
-
Verify the Liberty Repository feature is enabledExamine the server.xml configuration file in the Liberty Profile usr/servers/<serverName>/ directory and look for features defined in the <featureManager> section. Specifically search for repository-related features such as 'libertyRepository-1.0' or similar repository featuresAffected if The repository feature (libertyRepository-1.0 or equivalent) is listed in the <featureManager> section of server.xml
-
Check for remote user authentication accessReview server.xml and the associated basicRegistry or LDAP configuration to determine if remote users can authenticate to the Liberty administrative endpointsAffected if Remote authentication is enabled and users can access the administrative REST APIs for feature management
You are affected if you are running IBM WebSphere Application Server Liberty Profile 8.5.x before 8.5.5.3 AND have the Liberty Repository feature enabled with remote authentication accessible to users.
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 to IBM WebSphere Application Server Liberty Profile 8.5.5.3 or later. Additionally, restrict and audit access to the feature installation functionality to only trusted administrators.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4767 — 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-2014-4767 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