dbcve.org
E BelediyeApplication · Eskom

CVE-2023-1114

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to 1.0.0.100 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Eskom e-Belediye allows Information Elicitation. This issue affects e-Belediye: from 1.0.0.95 before 1.0.0.100.

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 · moderate confidence

Missing Authorization vulnerability in Eskom e-Belediye allows unauthenticated or unauthorized users to access sensitive information through the application. The flaw exists in versions 1.0.0.95 through before 1.0.0.100, where certain endpoints or functions lack proper access controls, enabling information elicitation/disclosure.

MitigationUpgrade e-Belediye to version 1.0.0.100 or later. If immediate upgrade is not possible, implement compensating controls such as network segmentation and API gateway authentication layers to restrict unauthorized access to vulnerable endpoints.

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
E BelediyeApplication
Affected:>= 1.0.0.95, < 1.0.0.100

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed e-Belediye version
    Access the application version information through the admin panel, version endpoint, or check version metadata files in the application directory. Compare this to the affected range 1.0.0.95 through 1.0.0.99.
    Affected if The installed version is 1.0.0.95, 1.0.0.96, 1.0.0.97, 1.0.0.98, or 1.0.0.99.
  2. Locate the application's endpoint configuration
    Examine the web server configuration or application routing files to identify accessible endpoints and their access control settings.
    Affected if Endpoints related to sensitive data retrieval do not have authorization checks configured.
  3. Test unauthenticated access to sensitive endpoints
    Attempt to access data retrieval endpoints without providing valid authentication credentials. Observe whether the application returns sensitive information.
    Affected if The application returns sensitive data or allows access to protected resources without authentication.
  4. Review access control definitions
    Inspect the application's access control configuration files or security module settings to verify which endpoints enforce authorization.
    Affected if Certain endpoints or functions are missing access control rules or have authorization disabled.

The environment is affected if the installed e-Belediye version is between 1.0.0.95 and 1.0.0.99 inclusive, and unauthenticated access to sensitive endpoints is possible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.0.100 or later
Fixed in 1.0.0.100
Interim mitigation

Upgrade e-Belediye to version 1.0.0.100 or later. If immediate upgrade is not possible, implement compensating controls such as network segmentation and API gateway authentication layers to restrict unauthorized access to vulnerable endpoints.

Recommended fix High confidence

Upgrade to E Belediye version 1.0.0.100 or later

  1. Identify the current installed version of E Belediye
  2. Obtain version 1.0.0.100 or later from the vendor (Eskom)
  3. Backup the current installation and any associated data
  4. Test the upgrade in a non-production environment first
  5. Schedule a maintenance window
  6. Apply the upgrade to version 1.0.0.100
  7. Verify the installation was successful and the vulnerability is fixed
Caveat Review release notes from vendor for any configuration or compatibility changes in version 1.0.0.100

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in E Belediye Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1114 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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