dbcve.org
ScooldApplication · Erudika

CVE-2024-50334

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to after 1.64.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Scoold is a Q&A and a knowledge sharing platform for teams. A semicolon path injection vulnerability was found on the /api;/config endpoint. By appending a semicolon in the URL, attackers can bypass authentication and gain unauthorised access to sensitive configuration data. Furthermore, PUT requests on the /api;/config endpoint while setting the Content-Type: application/hocon header allow unauthenticated attackers to file reading via HOCON file inclusion. This allows attackers to retrieve sensitive information such as configuration files from the server, which can be leveraged for further exploitation. The vulnerability has been fixed in Scoold 1.64.0. A workaround would be to disable the Scoold API with scoold.api_enabled = false.

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 confidence

Semicolon path injection in /api;/config bypasses authentication, allowing unauthorized access to sensitive configuration data. Additionally, PUT requests with Content-Type: application/hocon enable unauthenticated file inclusion, permitting attackers to read arbitrary files from the server.

MitigationUpgrade to Scoold 1.64.0 or disable the API by setting scoold.api_enabled = false as a workaround.

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
ScooldApplication
Affected:<= 1.64.0

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

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

  1. Confirm Scoold is deployed
    Identify if Erudika Scoold is running in your environment by checking for Scoold processes, JAR files, or the application running on its typical port (8000 by default). Look for scoold.jar or the application banner on startup.
    Affected if Scoold is running in your environment
  2. Identify installed Scoold version
    Check the version of the deployed Scoold instance. This is typically visible in the application startup logs, or by examining the JAR file properties (jar tf scoold.jar | grep version), or checking the pom.xml if source is available. Compare against the affected range: <= 1.64.0
    Affected if Installed version is 1.64.0 or lower
  3. Verify API is enabled
    Examine the Scoold configuration file (application.conf, application.properties, or environment variables) for the setting scoold.api_enabled. Check if it is set to true or if it defaults to true (not explicitly set to false).
    Affected if scoold.api_enabled is not explicitly set to false (API is accessible)
  4. Test semicolon path injection endpoint
    Send an HTTP GET request to /api;/config (note the semicolon in the path) without any authentication headers. Observe if the response returns sensitive configuration data or authentication bypass succeeds.
    Affected if Request to /api;/config returns configuration data without authentication
  5. Test HOCON file inclusion vulnerability
    Send an HTTP PUT request with Content-Type: application/hocon header to an API endpoint, attempting to include a file path (e.g., using include required("file:///etc/passwd") syntax in the request body). Check if arbitrary file content is returned.
    Affected if PUT with Content-Type: application/hocon returns contents of arbitrary server files

If Scoold version is 1.64.0 or lower, the API is enabled, and either the /api;/config path returns unauthenticated data or PUT requests with application/hocon Content-Type can read arbitrary files, the environment is affected by CVE-2024-50334.

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 a release after 1.64.0
Interim mitigation

Upgrade to Scoold 1.64.0 or disable the API by setting scoold.api_enabled = false as a workaround.

Recommended fix High confidence

Scoold 1.64.0 or later

  1. 1. Back up your current Scoold configuration and data
  2. 2. Check the current Scoold version running in your environment
  3. 3. Upgrade Scoold to version 1.64.0 or later (the version containing the security fix)
  4. 4. After upgrade, verify the /api;/config endpoint is no longer accessible without authentication
  5. 5. Test that legitimate API functionality still works as expected

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

Fix this in Scoold Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50334 — 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-2024-50334 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