FKIE_CVE-2023-4509

Vulnerability from fkie_nvd - Published: 2024-04-18 00:15 - Updated: 2026-06-17 06:37
Severity
4.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Summary
It is possible for an API key to be logged in clear text in the audit log file after an invalid login attempt.
References
security@octopus.comhttps://advisories.octopus.com/post/2024/sa2024-02/Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://advisories.octopus.com/post/2024/sa2024-02/Vendor Advisory
Impacted products
Vendor Product Version
octopus octopus_server *
linux linux_kernel -
microsoft windows -
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "platforms": [
            "Windows",
            "Linux"
          ],
          "product": "Octopus Server",
          "vendor": "Octopus Deploy",
          "versions": [
            {
              "lessThan": "2023.4.296",
              "status": "affected",
              "version": "2018.9",
              "versionType": "custom"
            },
            {
              "lessThan": "2024.1.437",
              "status": "affected",
              "version": "2024.1",
              "versionType": "custom"
            },
            {
              "lessThan": "2024.2.101",
              "status": "affected",
              "version": "2024.2",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "security@octopus.com"
    },
    {
      "affectedData": [
        {
          "cpes": [
            "cpe:2.3:a:octopus:octopus_server:-:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unknown",
          "product": "octopus_server",
          "vendor": "octopus",
          "versions": [
            {
              "lessThan": "2024.2.101",
              "status": "affected",
              "version": "2024.2",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:octopus:octopus_server:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "C7EC8A88-1A52-440F-9115-0E4DBF079038",
              "versionEndExcluding": "2023.4.296",
              "versionStartIncluding": "2018.9.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        },
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "703AF700-7A70-47E2-BC3A-7FD03B3CA9C1",
              "vulnerable": false
            },
            {
              "criteria": "cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "A2572D17-1DE6-457B-99CC-64AFD54487EA",
              "vulnerable": false
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ],
      "operator": "AND"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "It is possible for an API key to be logged in clear text in the audit log file after an invalid login attempt."
    },
    {
      "lang": "es",
      "value": "Es posible que una clave API se registre en texto plano en el archivo de registro de auditor\u00eda despu\u00e9s de un intento de inicio de sesi\u00f3n no v\u00e1lido."
    }
  ],
  "id": "CVE-2023-4509",
  "lastModified": "2026-06-17T06:37:59.307",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 4.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 1.4,
        "source": "security@octopus.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2023-4509",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2024-04-23T19:18:35.698764Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2024-04-18T00:15:07.340",
  "references": [
    {
      "source": "security@octopus.com",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://advisories.octopus.com/post/2024/sa2024-02/"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://advisories.octopus.com/post/2024/sa2024-02/"
    }
  ],
  "sourceIdentifier": "security@octopus.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-319"
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON

Loading timeline…




    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.