FKIE_CVE-2024-21684
Vulnerability from fkie_nvd - Published: 2024-07-24 18:15 - Updated: 2026-06-17 07:09| URL | Tags | ||
|---|---|---|---|
| security@atlassian.com | https://jira.atlassian.com/browse/BSERV-19454 | Issue Tracking, Vendor Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://jira.atlassian.com/browse/BSERV-19454 | Issue Tracking, Vendor Advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| atlassian | bitbucket_data_center | * | |
| atlassian | bitbucket_data_center | * |
{
"affected": [
{
"affectedData": [
{
"product": "Bitbucket Data Center",
"vendor": "Atlassian",
"versions": [
{
"status": "affected",
"version": "8.19.1"
},
{
"status": "affected",
"version": "8.9.0 to 8.9.12"
},
{
"status": "affected",
"version": "8.8.0 to 8.8.7"
},
{
"status": "affected",
"version": "8.7.0 to 8.7.5"
},
{
"status": "affected",
"version": "8.6.0 to 8.6.4"
},
{
"status": "affected",
"version": "8.5.0 to 8.5.4"
},
{
"status": "affected",
"version": "8.4.0 to 8.4.4"
},
{
"status": "affected",
"version": "8.3.0 to 8.3.4"
},
{
"status": "affected",
"version": "8.2.2 to 8.2.4"
},
{
"status": "affected",
"version": "8.1.3 to 8.1.5"
},
{
"status": "affected",
"version": "8.0.3 to 8.0.5"
},
{
"status": "unaffected",
"version": "8.19.2 to 8.19.6"
},
{
"status": "unaffected",
"version": "8.9.13 to 8.9.17"
}
]
}
],
"source": "security@atlassian.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:atlassian:bitbucket_data_center:*:*:*:*:*:*:*:*",
"matchCriteriaId": "11D36FB5-005E-4885-92E6-D7CB33C20640",
"versionEndExcluding": "8.9.13",
"versionStartIncluding": "8.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:atlassian:bitbucket_data_center:*:*:*:*:*:*:*:*",
"matchCriteriaId": "DACEEFBB-7E18-44F2-B853-4AF6731EF5CA",
"versionEndExcluding": "8.19.2",
"versionStartIncluding": "8.19.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "There is a low severity open redirect vulnerability within affected versions of Bitbucket Data Center. Versions of Bitbucket DC from 8.0.0 to 8.9.12 and 8.19.0 to 8.19.1 are affected by this vulnerability. It is patched in 8.9.13 and 8.19.2.\n\nThis open redirect vulnerability, with a CVSS Score of 3.1 and a CVSS Vector of CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N, allows an unauthenticated attacker to redirect a victim user upon login to Bitbucket Data Center to any arbitrary site which can be utilized for further exploitation which has low impact to confidentiality, no impact to integrity, no impact to availability, and requires user interaction.\n\nAtlassian recommends that Bitbucket Data Center customers upgrade to the version. If you are unable to do so, upgrade your instance to one of the supported fixed versions."
},
{
"lang": "es",
"value": "Existe una vulnerabilidad de redireccionamiento abierto de baja gravedad en las versiones afectadas de Bitbucket Data Center. Las versiones de Bitbucket DC de 8.0.0 a 8.9.12 y de 8.19.0 a 8.19.1 se ven afectadas por esta vulnerabilidad. Est\u00e1 parcheado en 8.9.13 y 8.19.2. Esta vulnerabilidad de redireccionamiento abierto, con una puntuaci\u00f3n CVSS de 3.1 y un vector CVSS de CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A: N, permite a un atacante no autenticado redirigir a un usuario v\u00edctima al iniciar sesi\u00f3n en Bitbucket Data Center a cualquier sitio arbitrario que pueda utilizarse para una mayor explotaci\u00f3n, lo que tiene un bajo impacto en la confidencialidad, ning\u00fan impacto en la integridad, ning\u00fan impacto en la disponibilidad y requiere la interacci\u00f3n del usuario. Atlassian recomienda que los clientes de Bitbucket Data Center actualicen a la versi\u00f3n. Si no puede hacerlo, actualice su instancia a una de las versiones fijas admitidas."
}
],
"id": "CVE-2024-21684",
"lastModified": "2026-06-17T07:09:58.960",
"metrics": {
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 3.1,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N",
"version": "3.0"
},
"exploitabilityScore": 1.6,
"impactScore": 1.4,
"source": "security@atlassian.com",
"type": "Secondary"
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-21684",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-07-24T18:45:18.293627Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-07-24T18:15:03.793",
"references": [
{
"source": "security@atlassian.com",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://jira.atlassian.com/browse/BSERV-19454"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://jira.atlassian.com/browse/BSERV-19454"
}
],
"sourceIdentifier": "security@atlassian.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-601"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.