← SECOM Trust Systems CO., LTD. cases
Bugzilla #1548714 Self Reported Incident

SECOM: "Default City" in Subject:localityName

RESOLVED FIXED SECOM Trust Systems CO., LTD.
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

SECOM Trust Systems CO., LTD. identified a compliance issue where 24 certificates contained 'Default City' in the localityName field, which was not validated according to the Baseline Requirements. The issue was discovered after a notification from the mozilla.dev-security-policy mailing list on May 7, 2019. SECOM initiated revocation of the affected certificates, completing the process by May 16, 2019. They also implemented system modifications to prevent future occurrences of this issue, including prohibiting the issuance of certificates with 'Default City' in the localityName field. An incident report detailing the actions taken was provided to Mozilla.

Model: gpt-4o-mini Generated: 2026-06-13 18:11 UTC Revised: 2026-06-16 18:43 UTC Confidence: 0.90 13 comments
Chronology
  1. List of SECOM certificates with 'Default City' published.
  2. SECOM became aware of the issue and began revocation.
  3. 20 out of 24 problematic certificates were revoked.
  4. Final problematic certificate was revoked.
  5. System improvements completed to prevent future issues.
Thread Activity
  1. Fastly representative — Reported SECOM certificates with 'Default City' in localityName.
  2. Secom representative — SECOM acknowledged the issue and began revocation.
  3. Secom representative — Provided incident report detailing actions taken.
  4. Secom representative — Confirmed completion of revocation of all problematic certificates.
  5. Secom representative — Reported completion of system modifications to prevent future issues.
Participants
Fastly representative Secom representative Community commenter
Similar Local Cases
#1391064 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-08-16 · Closed 2023-02-22 · 100% similar
SECOM: Non-BR-Compliant Certificate Issuance
#1544712 RESOLVED Self Reported Incident Opened 2019-04-16 · Closed 2023-02-22 · 100% similar
SECOM: certificate for which “OU=-”
#1560234 RESOLVED Self Reported Incident Opened 2019-06-20 · Closed 2022-11-14 · 100% similar
SECOM: Ambiguity on KeyUsage with ECC public key
#1563574 RESOLVED Self Reported Incident Opened 2019-07-04 · Closed 2023-02-22 · 100% similar
SECOM: Failure to disclose Unconstrained Intermediate within 7 Days
#1398259 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-09-08 · Closed 2023-02-22 · 99% similar
SECOM: Non-BR-Compliant OCSP Responders
#1524452 RESOLVED Self Reported Incident Opened 2019-02-01 · Closed 2023-02-22 · 97% similar
SECOM: certificate for .test TLD
#1497703 RESOLVED Self Reported Incident Certificate Misissuance Closure Request Opened 2018-10-09 · Closed 2023-02-22 · 96% similar
SECOM: Undisclosed intermediate certificates
#1576133 RESOLVED Self Reported Incident Opened 2019-08-23 · Closed 2023-02-22 · 86% similar
SECOM: Mis-issued EV Certificates

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action