dbcve.org
OstickyApplication · Smartcalc

CVE-2024-21728

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to 2.2.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
An Open Redirect vulnerability was found in osTicky2 below 2.2.8. osTicky (osTicket Bridge) by SmartCalc is a Joomla 3.x extension that provides Joomla fronted integration with osTicket, a popular Support ticket system. The Open Redirect vulnerability allows attackers to control the return parameter in the URL to a base64 malicious URL.

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

Open Redirect vulnerability in osTicky2 (Joomla osTicket Bridge extension) allows attackers to control a 'return' URL parameter containing a base64-encoded malicious URL. When users are redirected through this parameter, they can be sent to attacker-controlled external sites instead of legitimate internal locations.

MitigationUpgrade to osTicky2 version 2.2.8 or later. Additionally, implement strict validation of the return parameter to ensure decoded URLs point only to trusted internal domains before performing redirects.

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
OstickyApplication
Affected:< 2.2.8

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 osTicky2 extension is installed
    In Joomla admin panel, navigate to Extensions > Manage and search for 'osTicky' or 'Smartcalc Osticky'. Alternatively, check the /components/com_osticky directory exists on the web server.
    Affected if The extension is found in Joomla or the component directory exists on the server
  2. Determine installed version
    In Joomla admin, go to Extensions > Manage > Install, locate osTicky2 and view version details. Alternatively, check the manifest XML file at /components/com_osticky/osticky.xml for the <version> tag.
    Affected if The version number is lower than 2.2.8
  3. Verify component is enabled and accessible
    In Joomla admin, go to Components > osTicky2 and confirm the component loads without errors. Also verify the component is published in the backend.
    Affected if The component is enabled and accessible to users
  4. Identify redirect functionality using return parameter
    Check the component's source files for redirect logic using the 'return' parameter. Look in controller files or view files for code handling base64-encoded URLs being used in redirects (functions like base64_decode followed by header redirect or JFactory::getApplication()->redirect).
    Affected if Code exists that decodes a 'return' parameter and uses it in a redirect without strict domain validation

A user is affected if osTicky2/Smartcalc Osticky is installed with a version below 2.2.8 and the component is enabled, allowing the vulnerable redirect functionality to be exploited via the base64-encoded return parameter.

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 2.2.8 or later
Fixed in 2.2.8
Interim mitigation

Upgrade to osTicky2 version 2.2.8 or later. Additionally, implement strict validation of the return parameter to ensure decoded URLs point only to trusted internal domains before performing redirects.

Recommended fix Moderate confidence

osTicky version 2.2.8

  1. Backup your Joomla site and database before making any changes
  2. Download osTicky version 2.2.8 (or latest available version) from the official Joomla Extensions Directory or the vendor's official source
  3. Log in to your Joomla Administrator dashboard
  4. Navigate to Extensions > Manage > Install
  5. Upload and install the updated osTicky extension package
  6. Verify the installation was successful by checking the installed version in Extensions > Manage > Discover or in the osTicky component
  7. Clear any Joomla and browser caches
  8. Test that the return/redirection functionality works correctly with the updated version

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

Fix this in Osticky Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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